Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5cc67d3821ae78f4a4931c8cbc81a3c2e2a0aefb53d4f91980f9b15f97437da0

Tx prefix hash: 163363eb57ce07b1eff63703445cf9a5a1ae15dd9f9ce68835c8e0fef7d5d49a
Tx public key: 5ba62589090230de5ee80dbcf5afafeff6c9a05edf1f6b1d9921ec4749da2d24
Timestamp: 1703835883 Timestamp [UCT]: 2023-12-29 07:44:43 Age [y:d:h:m:s]: 01:137:16:32:27
Block: 923546 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 359547 RingCT/type: yes/0
Extra: 015ba62589090230de5ee80dbcf5afafeff6c9a05edf1f6b1d9921ec4749da2d2402110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 17d0b37d047f9d5b74e4a5d4193e7aff71557a54913c176cd4e7a11c08a3a406 0.600000000000 1381278 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": 923556, "vin": [ { "gen": { "height": 923546 } } ], "vout": [ { "amount": 600000000, "target": { "key": "17d0b37d047f9d5b74e4a5d4193e7aff71557a54913c176cd4e7a11c08a3a406" } } ], "extra": [ 1, 91, 166, 37, 137, 9, 2, 48, 222, 94, 232, 13, 188, 245, 175, 175, 239, 246, 201, 160, 94, 223, 31, 107, 29, 153, 33, 236, 71, 73, 218, 45, 36, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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