Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 72c5a1ff7b80cb3b91dab478ff02d223622ec326f2dbd88c07e381ad2d18f22d

Tx prefix hash: 7bf801cdf238fc278e9eba93d3e009d4582d1efbf9e7f30c55b17ecf95b07e61
Tx public key: 765c46f52e9939917e57c17cd8502827e489a72658b55fc832f1c73aa63296ab
Timestamp: 1713947097 Timestamp [UCT]: 2024-04-24 08:24:57 Age [y:d:h:m:s]: 00:306:15:10:41
Block: 1007382 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219164 RingCT/type: yes/0
Extra: 01765c46f52e9939917e57c17cd8502827e489a72658b55fc832f1c73aa63296ab0211000000017a9cf4c7000000000000000000

1 output(s) for total of 0.615620000000 dcy

stealth address amount amount idx
00: 0f9313bad2ff25a2a9b7f8a5762adef2c193f70d4af4c02fee4a941854372af5 0.615620000000 1468702 of 0

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": 1007392, "vin": [ { "gen": { "height": 1007382 } } ], "vout": [ { "amount": 615620000, "target": { "key": "0f9313bad2ff25a2a9b7f8a5762adef2c193f70d4af4c02fee4a941854372af5" } } ], "extra": [ 1, 118, 92, 70, 245, 46, 153, 57, 145, 126, 87, 193, 124, 216, 80, 40, 39, 228, 137, 167, 38, 88, 181, 95, 200, 50, 241, 199, 58, 166, 50, 150, 171, 2, 17, 0, 0, 0, 1, 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