Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: a65f55999b6a06853a583d4643311a117cf8baecfa47134861f462584b17af55

Tx prefix hash: fd186da94e734540048e0a1f0bc4b86e96be3fa34ae837034168cb4be106938e
Tx public key: afd6d38936590a9a88cd9bfa6a232dafb5028baa830743b66955cf11f8b6a6a4
Timestamp: 1701228959 Timestamp [UCT]: 2023-11-29 03:35:59 Age [y:d:h:m:s]: 01:133:19:09:45
Block: 901930 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356788 RingCT/type: yes/0
Extra: 01afd6d38936590a9a88cd9bfa6a232dafb5028baa830743b66955cf11f8b6a6a402110000000675e3f0e9000000000000000000

1 output(s) for total of 0.630277033000 dcy

stealth address amount amount idx
00: c8f003444fc8e5dc9841f13bd432c3efd63a6d694984799cf1d4fd67bb91c941 0.630277033000 1358529 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": 901940, "vin": [ { "gen": { "height": 901930 } } ], "vout": [ { "amount": 630277033, "target": { "key": "c8f003444fc8e5dc9841f13bd432c3efd63a6d694984799cf1d4fd67bb91c941" } } ], "extra": [ 1, 175, 214, 211, 137, 54, 89, 10, 154, 136, 205, 155, 250, 106, 35, 45, 175, 181, 2, 139, 170, 131, 7, 67, 182, 105, 85, 207, 17, 248, 182, 166, 164, 2, 17, 0, 0, 0, 6, 117, 227, 240, 233, 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