Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ee1c2eb417fcbc962fea971eeaf0bd13e0205d332296f2ca2df0b0ff57772ead

Tx prefix hash: a2b05f27fd035ab75cb72b8973bf0a40fd3f874c6b67192850f84fd4e65a07be
Tx public key: 368d61bcea1bd7726e6b1602263dd46cfca41d873fb8228ff484868e87c2fc68
Timestamp: 1697021583 Timestamp [UCT]: 2023-10-11 10:53:03 Age [y:d:h:m:s]: 01:189:19:18:25
Block: 867256 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 396696 RingCT/type: yes/0
Extra: 01368d61bcea1bd7726e6b1602263dd46cfca41d873fb8228ff484868e87c2fc6802110000000136a45730000000000000000000

1 output(s) for total of 0.821146958000 dcy

stealth address amount amount idx
00: 58a8aa5f48cd9d20fca01e4fbd21109a516cd3eba1ca52c3d4f5a764ebc2c459 0.821146958000 1321930 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": 867266, "vin": [ { "gen": { "height": 867256 } } ], "vout": [ { "amount": 821146958, "target": { "key": "58a8aa5f48cd9d20fca01e4fbd21109a516cd3eba1ca52c3d4f5a764ebc2c459" } } ], "extra": [ 1, 54, 141, 97, 188, 234, 27, 215, 114, 110, 107, 22, 2, 38, 61, 212, 108, 252, 164, 29, 135, 63, 184, 34, 143, 244, 132, 134, 142, 135, 194, 252, 104, 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