Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: dd3c23d58187874bec274c694b395e4986a1783ed4fd9d2f911655647cc59ca4

Tx prefix hash: 12cd028e8869b31cc4f6722054a6b111a64b55239684c505f48671a6b12ab24b
Tx public key: c08aba44cbc8d60dfe5e7448956ba14e81dc88e5dd9179a28b4226e8d28e5525
Timestamp: 1707401259 Timestamp [UCT]: 2024-02-08 14:07:39 Age [y:d:h:m:s]: 00:318:16:03:30
Block: 953094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 228184 RingCT/type: yes/0
Extra: 01c08aba44cbc8d60dfe5e7448956ba14e81dc88e5dd9179a28b4226e8d28e55250211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d621315adf6d7c4fb25d42ce2d0d2629084cb89ec31f5e7e3d0ff4475e943355 0.600000000000 1412258 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": 953104, "vin": [ { "gen": { "height": 953094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d621315adf6d7c4fb25d42ce2d0d2629084cb89ec31f5e7e3d0ff4475e943355" } } ], "extra": [ 1, 192, 138, 186, 68, 203, 200, 214, 13, 254, 94, 116, 72, 149, 107, 161, 78, 129, 220, 136, 229, 221, 145, 121, 162, 139, 66, 38, 232, 210, 142, 85, 37, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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