Dinastycoin Blockchain Explorer

(no javascript - no cookies - no web analytics trackers - no images - open sourced)

Autorefresh is OFF

Tx hash: 3445e866e56a79620b7c990cab974d072d558a69f7552351ff8f612f7acb592b

Tx prefix hash: 8fb20db8fc717deb203afeafafd3a3bcf391ac8c6b616bb05a73232061903514
Tx public key: e56316f4a44638e699513eeeef5b041c17e8c85a0868bf0f86b9a2430b1467f6
Timestamp: 1727717969 Timestamp [UCT]: 2024-09-30 17:39:29 Age [y:d:h:m:s]: 00:114:21:00:41
Block: 1121544 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 82092 RingCT/type: yes/0
Extra: 01e56316f4a44638e699513eeeef5b041c17e8c85a0868bf0f86b9a2430b1467f602110000000591e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1f2a41c6df6a8872926131c1ee9749255998e483f0da2e1f708d785e79166b4c 0.600000000000 1603833 of 15

Check which outputs belong to given Dinastycoin address/subaddress and viewkey

For RingCT transactions, outputs' amounts are also decoded
Note: address/subaddress and viewkey are sent to the server, as the calculations are done on the server side



Prove to someone that you have sent them Dinastycoin in this transaction

Tx private key can be obtained using get_tx_key command in dinasty-wallet-cli command line tool
Note: address/subaddress and tx private key are sent to the server, as the calculations are done on the server side



{ "version": 2, "unlock_time": 1121554, "vin": [ { "gen": { "height": 1121544 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1f2a41c6df6a8872926131c1ee9749255998e483f0da2e1f708d785e79166b4c" } } ], "extra": [ 1, 229, 99, 22, 244, 164, 70, 56, 230, 153, 81, 62, 238, 239, 91, 4, 28, 23, 232, 200, 90, 8, 104, 191, 15, 134, 185, 162, 67, 11, 20, 103, 246, 2, 17, 0, 0, 0, 5, 145, 225, 60, 4, 0, 0, 0, 0, 0, 0, 0, 0, 0 ], "rct_signatures": { "type": 0 } }


Less details
source code | explorer version (api): master-2022-04-20-3036769 (1.2) | dinastycoin version: 4.1-b41cfa2b8