Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: b87bb16d041234e9327cc34226d2c879917e7e5a06dd8d3a76b8b141b7e2c6b4

Tx prefix hash: cc68689f694b17a0d0ff9e2dccecd9b8d28aaf8da1bf379b97936014fcd9e2f8
Tx public key: 522b17f2fc7d3ab6c7778d0a9a38315689a1541a1a9f7d0dcbecd083b57bf201
Timestamp: 1647459801 Timestamp [UCT]: 2022-03-16 19:43:21 Age [y:d:h:m:s]: 02:362:04:03:58
Block: 459877 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 778149 RingCT/type: yes/0
Extra: 01522b17f2fc7d3ab6c7778d0a9a38315689a1541a1a9f7d0dcbecd083b57bf201021100000007c9067537000000000000000000

1 output(s) for total of 18.375402437000 dcy

stealth address amount amount idx
00: 522b00d7fb0b82cbc1217364989f4da6670d8348f398a0b9c6c81fcef5009124 18.375402437000 876734 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": 459887, "vin": [ { "gen": { "height": 459877 } } ], "vout": [ { "amount": 18375402437, "target": { "key": "522b00d7fb0b82cbc1217364989f4da6670d8348f398a0b9c6c81fcef5009124" } } ], "extra": [ 1, 82, 43, 23, 242, 252, 125, 58, 182, 199, 119, 141, 10, 154, 56, 49, 86, 137, 161, 84, 26, 26, 159, 125, 13, 203, 236, 208, 131, 181, 123, 242, 1, 2, 17, 0, 0, 0, 7, 201, 6, 117, 55, 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