Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 8700bc8421e572b5362f6fa2b5b2af908c35a36134664a5bfaedeab915a9963d

Tx prefix hash: 3a2481cbc5dc54abd906f940e058b0ed587403d0be68df7313825e18960f2cf3
Tx public key: 985266b55af97f0cacfc4bd38a7e4f1bfd00cc5242d90a7c6eb660a6dd53d094
Timestamp: 1737706633 Timestamp [UCT]: 2025-01-24 08:17:13 Age [y:d:h:m:s]: 00:301:09:33:00
Block: 1204158 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 212946 RingCT/type: yes/0
Extra: 01985266b55af97f0cacfc4bd38a7e4f1bfd00cc5242d90a7c6eb660a6dd53d0940211000000071f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 2f38dec575e78163f4da2607902daa89c9f8485c187de9b718f8830fce3a8198 0.600000000000 1690841 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": 1204168, "vin": [ { "gen": { "height": 1204158 } } ], "vout": [ { "amount": 600000000, "target": { "key": "2f38dec575e78163f4da2607902daa89c9f8485c187de9b718f8830fce3a8198" } } ], "extra": [ 1, 152, 82, 102, 181, 90, 249, 127, 12, 172, 252, 75, 211, 138, 126, 79, 27, 253, 0, 204, 82, 66, 217, 10, 124, 110, 182, 96, 166, 221, 83, 208, 148, 2, 17, 0, 0, 0, 7, 31, 10, 83, 235, 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