Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61f00fb5dcda65c47d794fdfb139f094bdafa0f6997e08e38c3bd8159f96c85a

Tx prefix hash: 794fc65ae01e191b6f98169aa94149a9bdf2798950ce539a17e98f0ecb44642f
Tx public key: 6f4516c7d371747ab2a4818b4d67c94e48d2dc41a80df78e9b49ae26a04ba734
Timestamp: 1708573760 Timestamp [UCT]: 2024-02-22 03:49:20 Age [y:d:h:m:s]: 00:349:13:49:14
Block: 962829 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 249967 RingCT/type: yes/0
Extra: 016f4516c7d371747ab2a4818b4d67c94e48d2dc41a80df78e9b49ae26a04ba7340211000000050011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a2930763635c9e126f2716da9815c1ce30532019be4ccd662865d8b791c78f9d 0.600000000000 1422514 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": 962839, "vin": [ { "gen": { "height": 962829 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a2930763635c9e126f2716da9815c1ce30532019be4ccd662865d8b791c78f9d" } } ], "extra": [ 1, 111, 69, 22, 199, 211, 113, 116, 122, 178, 164, 129, 139, 77, 103, 201, 78, 72, 210, 220, 65, 168, 13, 247, 142, 155, 73, 174, 38, 160, 75, 167, 52, 2, 17, 0, 0, 0, 5, 0, 17, 5, 91, 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