Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4b927085bdf4e1e912db825c735ec8e891edb171eab68b50c387a039ebf4ec74

Tx prefix hash: 8354b63b5b5f81c48f532ebee97aa5cb8ffd7c0f4b1e326300628320d82dd5b2
Tx public key: b3d2c2aa639f28f284268d0a246f92ff8dc81d8e91587191c2987d595798056d
Timestamp: 1698387480 Timestamp [UCT]: 2023-10-27 06:18:00 Age [y:d:h:m:s]: 01:184:08:16:42
Block: 878598 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 392767 RingCT/type: yes/0
Extra: 01b3d2c2aa639f28f284268d0a246f92ff8dc81d8e91587191c2987d595798056d02110000000136a45730000000000000000000

1 output(s) for total of 0.753078272000 dcy

stealth address amount amount idx
00: 550cfe633293d34b5fc53c3552d01516494df3d3996f42195812a86282cf1c70 0.753078272000 1334056 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": 878608, "vin": [ { "gen": { "height": 878598 } } ], "vout": [ { "amount": 753078272, "target": { "key": "550cfe633293d34b5fc53c3552d01516494df3d3996f42195812a86282cf1c70" } } ], "extra": [ 1, 179, 210, 194, 170, 99, 159, 40, 242, 132, 38, 141, 10, 36, 111, 146, 255, 141, 200, 29, 142, 145, 88, 113, 145, 194, 152, 125, 89, 87, 152, 5, 109, 2, 17, 0, 0, 0, 1, 54, 164, 87, 48, 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