Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 71f0fd8efc6fbdef9118257c7b7c23066706304ad3a2b7213bfd21a539837d8c

Tx prefix hash: c1f8d9717453284cc15dc813242d02b7e9bd3d6d3678aa03e17cc4975955e5be
Tx public key: 55ad954dcb2811bd11786303940f428c2660160f3390dd457827dae7e2a6cf96
Timestamp: 1577823677 Timestamp [UCT]: 2019-12-31 20:21:17 Age [y:d:h:m:s]: 05:304:20:09:05
Block: 35993 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1365336 RingCT/type: yes/0
Extra: 0155ad954dcb2811bd11786303940f428c2660160f3390dd457827dae7e2a6cf9602110000004c398c17aa000000000000000000

1 output(s) for total of 466.381272560000 dcy

stealth address amount amount idx
00: 0083bd3b8dd2f1246f042ff364b23bdc886e12bcbd13b01041b24fc6de4ae716 466.381272560000 60811 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": 36003, "vin": [ { "gen": { "height": 35993 } } ], "vout": [ { "amount": 466381272560, "target": { "key": "0083bd3b8dd2f1246f042ff364b23bdc886e12bcbd13b01041b24fc6de4ae716" } } ], "extra": [ 1, 85, 173, 149, 77, 203, 40, 17, 189, 17, 120, 99, 3, 148, 15, 66, 140, 38, 96, 22, 15, 51, 144, 221, 69, 120, 39, 218, 231, 226, 166, 207, 150, 2, 17, 0, 0, 0, 76, 57, 140, 23, 170, 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