Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 981d18fd6fb23ee33548933967a796cfa5042848ea4f4daf9ca3188761622df6

Tx prefix hash: 3f1e0274079f6758c04918f9102d95a2c87fae4f92316ba0f9e71c46abe7d264
Tx public key: 2582963165af6061ba04f7897b8edee6e34a4d67a6257c122c26376bac2ea43c
Timestamp: 1717144726 Timestamp [UCT]: 2024-05-31 08:38:46 Age [y:d:h:m:s]: 00:307:12:25:44
Block: 1033889 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219769 RingCT/type: yes/0
Extra: 012582963165af6061ba04f7897b8edee6e34a4d67a6257c122c26376bac2ea43c02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 201a5e3a8535d88538117d4f8e2d3d269c478c1c0910208ec433367c2e233de4 0.600000000000 1502362 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": 1033899, "vin": [ { "gen": { "height": 1033889 } } ], "vout": [ { "amount": 600000000, "target": { "key": "201a5e3a8535d88538117d4f8e2d3d269c478c1c0910208ec433367c2e233de4" } } ], "extra": [ 1, 37, 130, 150, 49, 101, 175, 96, 97, 186, 4, 247, 137, 123, 142, 222, 230, 227, 74, 77, 103, 166, 37, 124, 18, 44, 38, 55, 107, 172, 46, 164, 60, 2, 17, 0, 0, 0, 2, 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