Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 54c0052b4edd611bc63f0b4e5b00d5d80b2ab1e027c946dec10e436a873d48d8

Tx prefix hash: d7c989db3948b80e40214e2054aa5206f119bbc84ece18d3da21d434ce6342a0
Tx public key: 6d5c91fd773f83551766874d08b8eeeb7456c1b7500a3e2752d5e085fef1cc26
Timestamp: 1737810540 Timestamp [UCT]: 2025-01-25 13:09:00 Age [y:d:h:m:s]: 00:048:02:50:00
Block: 1205018 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 34212 RingCT/type: yes/0
Extra: 016d5c91fd773f83551766874d08b8eeeb7456c1b7500a3e2752d5e085fef1cc26021100000001007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 1a3a46a9bec1165510e61dc5908a6b17445cd19291000ccac590d8a2f42970fc 0.600000000000 1691713 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": 1205028, "vin": [ { "gen": { "height": 1205018 } } ], "vout": [ { "amount": 600000000, "target": { "key": "1a3a46a9bec1165510e61dc5908a6b17445cd19291000ccac590d8a2f42970fc" } } ], "extra": [ 1, 109, 92, 145, 253, 119, 63, 131, 85, 23, 102, 135, 77, 8, 184, 238, 235, 116, 86, 193, 183, 80, 10, 62, 39, 82, 213, 224, 133, 254, 241, 204, 38, 2, 17, 0, 0, 0, 1, 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