Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 94b1a7ad8d543de3c66ccf430b66636b450e1994f2f1ccdf5e4e90fc05e10f40

Tx prefix hash: d745eec9cd536e15f67019eaf9912015dc3074a6861411b435da45dae84f1d97
Tx public key: d91cab5a59a9a4299009e5a72e1d2470ddea2aa0467ce3ed9b1172d5f5a3846a
Timestamp: 1751180246 Timestamp [UCT]: 2025-06-29 06:57:26 Age [y:d:h:m:s]: 00:144:14:54:34
Block: 1315043 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 101471 RingCT/type: yes/0
Extra: 01d91cab5a59a9a4299009e5a72e1d2470ddea2aa0467ce3ed9b1172d5f5a3846a021100000002e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 22a6ee42db256856927e64ae658441456c6e26bbbd9fb9fc2dd84b35c64b3ec4 0.600000000000 1802696 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": 1315053, "vin": [ { "gen": { "height": 1315043 } } ], "vout": [ { "amount": 600000000, "target": { "key": "22a6ee42db256856927e64ae658441456c6e26bbbd9fb9fc2dd84b35c64b3ec4" } } ], "extra": [ 1, 217, 28, 171, 90, 89, 169, 164, 41, 144, 9, 229, 167, 46, 29, 36, 112, 221, 234, 42, 160, 70, 124, 227, 237, 155, 17, 114, 213, 245, 163, 132, 106, 2, 17, 0, 0, 0, 2, 228, 220, 144, 9, 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