Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6eb5ea44272c0cf1764b95a57b8db15410731a6c72400aa8f6dbc51e46f1d229

Tx prefix hash: f043a5bf605c9efcf74eafece3ca8fcc1fb28a82ace74e827c89df938732cd5d
Tx public key: 18f6c1c43597243d479bdc5d6ec3d7acc8ccee6faafe48a37ab45cac8dd2c8a5
Timestamp: 1698614766 Timestamp [UCT]: 2023-10-29 21:26:06 Age [y:d:h:m:s]: 01:191:15:12:19
Block: 880478 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 397970 RingCT/type: yes/0
Extra: 0118f6c1c43597243d479bdc5d6ec3d7acc8ccee6faafe48a37ab45cac8dd2c8a5021100000005e6d27f9c000000000000000000

1 output(s) for total of 0.742353729000 dcy

stealth address amount amount idx
00: 0524e13b5f1de45fb402fa4022f4d4c23e3cfc34eb935a78f357d4bf4340d21e 0.742353729000 1336036 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": 880488, "vin": [ { "gen": { "height": 880478 } } ], "vout": [ { "amount": 742353729, "target": { "key": "0524e13b5f1de45fb402fa4022f4d4c23e3cfc34eb935a78f357d4bf4340d21e" } } ], "extra": [ 1, 24, 246, 193, 196, 53, 151, 36, 61, 71, 155, 220, 93, 110, 195, 215, 172, 200, 204, 238, 111, 170, 254, 72, 163, 122, 180, 92, 172, 141, 210, 200, 165, 2, 17, 0, 0, 0, 5, 230, 210, 127, 156, 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