Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4124df301ee00ba6fdecd983b0d9006068806d7b62b639a0a6d063a08fcecbb5

Tx prefix hash: 5c2acf374f7d6ecd6b59e89955a6ee02b5c7ac8b14cb1e8a67f17fdee82c0224
Tx public key: 67456efcc53c2ff5ec4ea46dd90545a1fcb57eb7afdb5bdf193a441eea8a89af
Timestamp: 1740912628 Timestamp [UCT]: 2025-03-02 10:50:28 Age [y:d:h:m:s]: 00:336:03:26:04
Block: 1230468 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 237913 RingCT/type: yes/0
Extra: 0167456efcc53c2ff5ec4ea46dd90545a1fcb57eb7afdb5bdf193a441eea8a89af02110000000a007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a14b3c33af60e402343fdd02436c82e1413a415262a46a0a9ebb2453496cfc04 0.600000000000 1717367 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": 1230478, "vin": [ { "gen": { "height": 1230468 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a14b3c33af60e402343fdd02436c82e1413a415262a46a0a9ebb2453496cfc04" } } ], "extra": [ 1, 103, 69, 110, 252, 197, 60, 47, 245, 236, 78, 164, 109, 217, 5, 69, 161, 252, 181, 126, 183, 175, 219, 91, 223, 25, 58, 68, 30, 234, 138, 137, 175, 2, 17, 0, 0, 0, 10, 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