Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d1044af5c8bcca1ce191805e19e5213f5caee726f28102bec29d698802570001

Tx prefix hash: 1b78437379b70744f05b17df43f9ba105f88d508c67ccdae79f88e5b948df78e
Tx public key: 9c2b7a8aa3e8810ea50c2a1b5a70b5e0e5c83ac385efc9f66a8ee66be6a25caf
Timestamp: 1725523464 Timestamp [UCT]: 2024-09-05 08:04:24 Age [y:d:h:m:s]: 00:262:07:22:21
Block: 1103349 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187356 RingCT/type: yes/0
Extra: 019c2b7a8aa3e8810ea50c2a1b5a70b5e0e5c83ac385efc9f66a8ee66be6a25caf021100000003e914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b4744cd3e2d8a9913321ec39b3e9b83bc3a11d41b915675ebc96eaee0da0e921 0.600000000000 1580144 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": 1103359, "vin": [ { "gen": { "height": 1103349 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b4744cd3e2d8a9913321ec39b3e9b83bc3a11d41b915675ebc96eaee0da0e921" } } ], "extra": [ 1, 156, 43, 122, 138, 163, 232, 129, 14, 165, 12, 42, 27, 90, 112, 181, 224, 229, 200, 58, 195, 133, 239, 201, 246, 106, 142, 230, 107, 230, 162, 92, 175, 2, 17, 0, 0, 0, 3, 233, 20, 221, 21, 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