Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 39add994ff9cfb347c1082c1d3177c512af30e7288d67a1cb215938317452429

Tx prefix hash: e8c1baa7344479dabf3aaf5b79d79257ef1bba2a0f17dfb6a735b173221682b7
Tx public key: 1d6ca213baef13b087e97d7cbd293fdf82689603da6199b8f69d215e8ee43ca2
Timestamp: 1715759045 Timestamp [UCT]: 2024-05-15 07:44:05 Age [y:d:h:m:s]: 00:331:02:00:13
Block: 1022393 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 236656 RingCT/type: yes/0
Extra: 011d6ca213baef13b087e97d7cbd293fdf82689603da6199b8f69d215e8ee43ca20211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: a72ebdaa99e132be8293f79865e4ea73e7d1b8b87111730d9787306c58c1092a 0.600000000000 1486982 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": 1022403, "vin": [ { "gen": { "height": 1022393 } } ], "vout": [ { "amount": 600000000, "target": { "key": "a72ebdaa99e132be8293f79865e4ea73e7d1b8b87111730d9787306c58c1092a" } } ], "extra": [ 1, 29, 108, 162, 19, 186, 239, 19, 176, 135, 233, 125, 124, 189, 41, 63, 223, 130, 104, 150, 3, 218, 97, 153, 184, 246, 157, 33, 94, 142, 228, 60, 162, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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