Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9627e4a53fb53bff61f43996c5ef881b4a551b543d3de73a2edec1edd2992344

Tx prefix hash: e4c59f554dcdaf8716e2f67669beb694d9ae4440ab49e43ba53b4712dfff90e4
Tx public key: 350d570b416a19fa02da201a3dfbc9b6e752d0e981d4f3849eca2952488285bf
Timestamp: 1659209325 Timestamp [UCT]: 2022-07-30 19:28:45 Age [y:d:h:m:s]: 02:286:10:21:25
Block: 555166 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 725939 RingCT/type: yes/0
Extra: 01350d570b416a19fa02da201a3dfbc9b6e752d0e981d4f3849eca2952488285bf02110000000575e3f0e9000000000000000000

1 output(s) for total of 8.882146013000 dcy

stealth address amount amount idx
00: 3d717da0e72cea24ff4f2c2317dd369baa963ab9bc0891085a3ba9ff7d86ad5e 8.882146013000 987050 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": 555176, "vin": [ { "gen": { "height": 555166 } } ], "vout": [ { "amount": 8882146013, "target": { "key": "3d717da0e72cea24ff4f2c2317dd369baa963ab9bc0891085a3ba9ff7d86ad5e" } } ], "extra": [ 1, 53, 13, 87, 11, 65, 106, 25, 250, 2, 218, 32, 26, 61, 251, 201, 182, 231, 82, 208, 233, 129, 212, 243, 132, 158, 202, 41, 82, 72, 130, 133, 191, 2, 17, 0, 0, 0, 5, 117, 227, 240, 233, 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