Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b1c2a7a8bffcfe3941ba545c93941190472cc2dd5ccf3c9fe2e3e647885bd90e

Tx prefix hash: bd63a7285c00d0481d370cbc10589d46ed98a3bccb12ef445644ee8d0162d1dd
Tx public key: 998e28be33c0f68faf3579ac79006b3415b9c63d84cdb0ff3a81bc8649aed61a
Timestamp: 1698382204 Timestamp [UCT]: 2023-10-27 04:50:04 Age [y:d:h:m:s]: 01:200:07:48:33
Block: 878555 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404196 RingCT/type: yes/0
Extra: 01998e28be33c0f68faf3579ac79006b3415b9c63d84cdb0ff3a81bc8649aed61a0211000000024b8f5122000000000000000000

1 output(s) for total of 0.753325371000 dcy

stealth address amount amount idx
00: a918b403b07ec3124b6e0931fadaa1a4ab3f29e4c3d9eff2755d2a2b9931d487 0.753325371000 1334007 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": 878565, "vin": [ { "gen": { "height": 878555 } } ], "vout": [ { "amount": 753325371, "target": { "key": "a918b403b07ec3124b6e0931fadaa1a4ab3f29e4c3d9eff2755d2a2b9931d487" } } ], "extra": [ 1, 153, 142, 40, 190, 51, 192, 246, 143, 175, 53, 121, 172, 121, 0, 107, 52, 21, 185, 198, 61, 132, 205, 176, 255, 58, 129, 188, 134, 73, 174, 214, 26, 2, 17, 0, 0, 0, 2, 75, 143, 81, 34, 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