Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 241c82214a1a1c3783cd0456773b1e294aafcb32b520d6f750d1246226a3e8c2

Tx prefix hash: c8a310c370df34b3862b9734646053b0c50229ec5c139c857e523c251be7de83
Tx public key: 75eccb44d2f2ddf8eedb58d15e75e1a80549ef96ec9c8f8fa6976dcc55dc3ca3
Timestamp: 1697444362 Timestamp [UCT]: 2023-10-16 08:19:22 Age [y:d:h:m:s]: 01:139:01:49:40
Block: 870761 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 360402 RingCT/type: yes/0
Extra: 0175eccb44d2f2ddf8eedb58d15e75e1a80549ef96ec9c8f8fa6976dcc55dc3ca302110000000d33af99f4000000000000000000

1 output(s) for total of 0.799479557000 dcy

stealth address amount amount idx
00: 1d8f9ecf5c015d3eca11b84e295c14d64f7091b9c9ebea5ca82287dd5f1beaa0 0.799479557000 1325648 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": 870771, "vin": [ { "gen": { "height": 870761 } } ], "vout": [ { "amount": 799479557, "target": { "key": "1d8f9ecf5c015d3eca11b84e295c14d64f7091b9c9ebea5ca82287dd5f1beaa0" } } ], "extra": [ 1, 117, 236, 203, 68, 210, 242, 221, 248, 238, 219, 88, 209, 94, 117, 225, 168, 5, 73, 239, 150, 236, 156, 143, 143, 166, 151, 109, 204, 85, 220, 60, 163, 2, 17, 0, 0, 0, 13, 51, 175, 153, 244, 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