Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1127611c0ff2614352d95fe1fb109518abce2f7b2cc84438e5cb4d89bd95022c

Tx prefix hash: bd11e8bfb1b2995fb62762f612d6a08a4eeafa3b0c17ff9deb3587bfb657ea7f
Tx public key: af3fc0387c12b91c13b9de0b5cbee7aafcb0ac5403b0a4dba897122d4cc73426
Timestamp: 1720981958 Timestamp [UCT]: 2024-07-14 18:32:38 Age [y:d:h:m:s]: 00:248:07:46:44
Block: 1065703 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 177412 RingCT/type: yes/0
Extra: 01af3fc0387c12b91c13b9de0b5cbee7aafcb0ac5403b0a4dba897122d4cc7342602110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bbc74bcc460208cfa34f9350c3c2732fd3413d38d256c8655308a974d744f237 0.600000000000 1536252 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": 1065713, "vin": [ { "gen": { "height": 1065703 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bbc74bcc460208cfa34f9350c3c2732fd3413d38d256c8655308a974d744f237" } } ], "extra": [ 1, 175, 63, 192, 56, 124, 18, 185, 28, 19, 185, 222, 11, 92, 190, 231, 170, 252, 176, 172, 84, 3, 176, 164, 219, 168, 151, 18, 45, 76, 199, 52, 38, 2, 17, 0, 0, 0, 3, 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