Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 66764c99395031e333639226ca05f90e1bbc55c59e744c64cf9b8f7d261fcc9c

Tx prefix hash: 6ecf7f1daa96537713b11478db217fb3e03409a58163598ac9129bfa8d30e2bf
Tx public key: 8f49a7d7eee1d8d52558f5b12c445d51a4d4f24a1f08b2dcf299c6223e932c6d
Timestamp: 1719203168 Timestamp [UCT]: 2024-06-24 04:26:08 Age [y:d:h:m:s]: 00:357:23:59:38
Block: 1050939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0811 kB
Tx version: 2 No of confirmations: 255764 RingCT/type: yes/0
Extra: 018f49a7d7eee1d8d52558f5b12c445d51a4d4f24a1f08b2dcf299c6223e932c6d

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7010b3828766d6a1ff1966b111a459262fab1b65e40de24212d3d1bce8439fec 0.600000000000 1521116 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": 1050949, "vin": [ { "gen": { "height": 1050939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7010b3828766d6a1ff1966b111a459262fab1b65e40de24212d3d1bce8439fec" } } ], "extra": [ 1, 143, 73, 167, 215, 238, 225, 216, 213, 37, 88, 245, 177, 44, 68, 93, 81, 164, 212, 242, 74, 31, 8, 178, 220, 242, 153, 198, 34, 62, 147, 44, 109 ], "rct_signatures": { "type": 0 } }


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