Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 79c9216c71efda5de214e582a19c5408feda08f9167f77165c772945ae958de3

Tx prefix hash: 4fc5077d2a640f35bbb6431f4a62355589fb0b0aed408e943f609836e56c7fff
Tx public key: 5862c04c02c1da7361e967bcc186d3b3d4e0915996b7f81d4a6f58d84a79483b
Timestamp: 1733425478 Timestamp [UCT]: 2024-12-05 19:04:38 Age [y:d:h:m:s]: 00:119:05:56:14
Block: 1168763 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 85020 RingCT/type: yes/0
Extra: 015862c04c02c1da7361e967bcc186d3b3d4e0915996b7f81d4a6f58d84a79483b0211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3407dd7a3bc02933260187759473cd02b82fa253f95a5dfc0ac0d94d78f62f89 0.600000000000 1654474 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": 1168773, "vin": [ { "gen": { "height": 1168763 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3407dd7a3bc02933260187759473cd02b82fa253f95a5dfc0ac0d94d78f62f89" } } ], "extra": [ 1, 88, 98, 192, 76, 2, 193, 218, 115, 97, 233, 103, 188, 193, 134, 211, 179, 212, 224, 145, 89, 150, 183, 248, 29, 74, 111, 88, 216, 74, 121, 72, 59, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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