Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7acbad1b4dd0a08f5b2844ec9700ca2e620c09ee0a04be44b38ddc548d666a4a

Tx prefix hash: fa4b68e89e4f87965e760fa26c77679fa666353a12752d8ffeaf40a9f9f0878e
Tx public key: 5cee889c729e2696e9f16059efb79f8c4f8bdf0db9b5bfcf6a516280ecd42959
Timestamp: 1727094971 Timestamp [UCT]: 2024-09-23 12:36:11 Age [y:d:h:m:s]: 00:199:20:04:34
Block: 1116381 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 142638 RingCT/type: yes/0
Extra: 015cee889c729e2696e9f16059efb79f8c4f8bdf0db9b5bfcf6a516280ecd4295902110000000191e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: d5f1090eb1b4014cea5e38dc55feb5c73c3b8d1292a5ada6353d9af67065f539 0.600000000000 1596840 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": 1116391, "vin": [ { "gen": { "height": 1116381 } } ], "vout": [ { "amount": 600000000, "target": { "key": "d5f1090eb1b4014cea5e38dc55feb5c73c3b8d1292a5ada6353d9af67065f539" } } ], "extra": [ 1, 92, 238, 136, 156, 114, 158, 38, 150, 233, 241, 96, 89, 239, 183, 159, 140, 79, 139, 223, 13, 185, 181, 191, 207, 106, 81, 98, 128, 236, 212, 41, 89, 2, 17, 0, 0, 0, 1, 145, 225, 60, 4, 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