Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 625d5cc4e9041fe5538641f8824a48375b74a4a3d4b7304bbd9b2a899cd086fa

Tx prefix hash: f47f29999c6894e880d38eb205e3e379ad9542e1eaee42623ca7dcdd1712ec65
Tx public key: 0f0a555964a8e506c5115b093d3722c5daaeca89ec210eafd5e951b49dafd710
Timestamp: 1703076763 Timestamp [UCT]: 2023-12-20 12:52:43 Age [y:d:h:m:s]: 01:101:18:36:03
Block: 917258 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 333851 RingCT/type: yes/0
Extra: 010f0a555964a8e506c5115b093d3722c5daaeca89ec210eafd5e951b49dafd7100211000000080011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 6f7c01303b99ce7c7e8a294eff2a2bb388bad4ced5ab04c065b2b5c40c77c55b 0.600000000000 1374828 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": 917268, "vin": [ { "gen": { "height": 917258 } } ], "vout": [ { "amount": 600000000, "target": { "key": "6f7c01303b99ce7c7e8a294eff2a2bb388bad4ced5ab04c065b2b5c40c77c55b" } } ], "extra": [ 1, 15, 10, 85, 89, 100, 168, 229, 6, 197, 17, 91, 9, 61, 55, 34, 197, 218, 174, 202, 137, 236, 33, 14, 175, 213, 233, 81, 180, 157, 175, 215, 16, 2, 17, 0, 0, 0, 8, 0, 17, 5, 91, 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