Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: cd3d2f900258b454040679b9cc0dadd68ad4fd2c4eed6035400acdb5071b48f2

Tx prefix hash: 9302736804e9366416ad7afc3e58e5b4279dcab88e5284038ef30516ee8f34f8
Tx public key: 193c9efd9b0a3e2ea495ba7df8e4962185381572510df56db0f40f0de9ba7052
Timestamp: 1707189364 Timestamp [UCT]: 2024-02-06 03:16:04 Age [y:d:h:m:s]: 01:299:20:56:48
Block: 951336 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 473129 RingCT/type: yes/0
Extra: 01193c9efd9b0a3e2ea495ba7df8e4962185381572510df56db0f40f0de9ba705202110000000959dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 54b3254332dd83756c3ecfdec2e828fb4b0da9dffd9421924c294bff11bf19f7 0.600000000000 1410088 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": 951346, "vin": [ { "gen": { "height": 951336 } } ], "vout": [ { "amount": 600000000, "target": { "key": "54b3254332dd83756c3ecfdec2e828fb4b0da9dffd9421924c294bff11bf19f7" } } ], "extra": [ 1, 25, 60, 158, 253, 155, 10, 62, 46, 164, 149, 186, 125, 248, 228, 150, 33, 133, 56, 21, 114, 81, 13, 245, 109, 176, 244, 15, 13, 233, 186, 112, 82, 2, 17, 0, 0, 0, 9, 89, 218, 211, 245, 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