Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 93df5e3f3d63b0b281d2ae86cc581f64a1914783d237082500ab7b9718baa0bb

Tx prefix hash: c4d637934666cf151089612674e4aecab51b7ebcc055aa5ced9240edb45dec8c
Tx public key: fa6b82dfc4c5c4174647a9c0758d8bd837a8df487663e96e0605d3fcde688ff5
Timestamp: 1577050711 Timestamp [UCT]: 2019-12-22 21:38:31 Age [y:d:h:m:s]: 04:332:00:40:58
Block: 29750 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1126228 RingCT/type: yes/0
Extra: 01fa6b82dfc4c5c4174647a9c0758d8bd837a8df487663e96e0605d3fcde688ff50211000000194943cd9f000000000000000000

1 output(s) for total of 489.158093374000 dcy

stealth address amount amount idx
00: 121b9f9ef41117c9c7cc62edf27b69f6d030d7b387d25301f7ea09cd7b215525 489.158093374000 49002 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": 29760, "vin": [ { "gen": { "height": 29750 } } ], "vout": [ { "amount": 489158093374, "target": { "key": "121b9f9ef41117c9c7cc62edf27b69f6d030d7b387d25301f7ea09cd7b215525" } } ], "extra": [ 1, 250, 107, 130, 223, 196, 197, 196, 23, 70, 71, 169, 192, 117, 141, 139, 216, 55, 168, 223, 72, 118, 99, 233, 110, 6, 5, 211, 252, 222, 104, 143, 245, 2, 17, 0, 0, 0, 25, 73, 67, 205, 159, 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