Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef8ec9a691b727c79deebf0a8c8c117444133ee65c7b775ed840b3c0bbd635d0

Tx prefix hash: 72ffbe8e4ae754f68c1c80a425fafb1e2c414b5e971fb14dc3d446b1a87a7a90
Tx public key: 083ac4beae86571e1fed031333619efb5fb6606c245f9326296dbf63eacc0555
Timestamp: 1741253867 Timestamp [UCT]: 2025-03-06 09:37:47 Age [y:d:h:m:s]: 00:093:22:15:01
Block: 1233306 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 67183 RingCT/type: yes/0
Extra: 01083ac4beae86571e1fed031333619efb5fb6606c245f9326296dbf63eacc055502110000000b007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 77b8e71df3c1d1124cf47af8194d04a04c0a464ad07777ca4ede8763613bc9a5 0.600000000000 1720225 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": 1233316, "vin": [ { "gen": { "height": 1233306 } } ], "vout": [ { "amount": 600000000, "target": { "key": "77b8e71df3c1d1124cf47af8194d04a04c0a464ad07777ca4ede8763613bc9a5" } } ], "extra": [ 1, 8, 58, 196, 190, 174, 134, 87, 30, 31, 237, 3, 19, 51, 97, 158, 251, 95, 182, 96, 108, 36, 95, 147, 38, 41, 109, 191, 99, 234, 204, 5, 85, 2, 17, 0, 0, 0, 11, 0, 127, 151, 138, 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