Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 413e08e8f7263e31888b84fb3208eb33a627af9d927d4aeca58ce6e24ffc79f6

Tx prefix hash: 68fedc39e97f15e82d2c11420edc17ed466ef44d2e2ba95ea9e7ce61c4b31c98
Tx public key: d817ce61a72898e5b3338c82d86b74ba63357d3ae28367c860199f8daddc161d
Timestamp: 1711760726 Timestamp [UCT]: 2024-03-30 01:05:26 Age [y:d:h:m:s]: 01:009:19:50:07
Block: 989266 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 267964 RingCT/type: yes/0
Extra: 01d817ce61a72898e5b3338c82d86b74ba63357d3ae28367c860199f8daddc161d0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b570f2ea3fe2c2725a9f3608cf17c29c14514e80b8d59287e4f0489133cfb033 0.600000000000 1449561 of 15

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": 989276, "vin": [ { "gen": { "height": 989266 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b570f2ea3fe2c2725a9f3608cf17c29c14514e80b8d59287e4f0489133cfb033" } } ], "extra": [ 1, 216, 23, 206, 97, 167, 40, 152, 229, 179, 51, 140, 130, 216, 107, 116, 186, 99, 53, 125, 58, 226, 131, 103, 200, 96, 25, 159, 141, 173, 220, 22, 29, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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