Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: abf0f485c86081ed45268a66bab2243c9746a97e6b0c6d0d91ecdbfcc62ec6f0

Tx prefix hash: b0c35f7d645b8c3692db10dceb9fa96bc57e9efcf2f24340b4d533b12d1ff569
Tx public key: 11ad9f6d369e98925111597b5214cb694ba241b666b4c2ae31565643f6dee2ca
Timestamp: 1702821327 Timestamp [UCT]: 2023-12-17 13:55:27 Age [y:d:h:m:s]: 01:034:02:53:41
Block: 915132 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 285705 RingCT/type: yes/0
Extra: 0111ad9f6d369e98925111597b5214cb694ba241b666b4c2ae31565643f6dee2ca021100000002faf35c9c000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 89a918f8496a70acb7b16f8e8bcb328e1485aaee94e647aefabaaff009cf9e50 0.600000000000 1372518 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": 915142, "vin": [ { "gen": { "height": 915132 } } ], "vout": [ { "amount": 600000000, "target": { "key": "89a918f8496a70acb7b16f8e8bcb328e1485aaee94e647aefabaaff009cf9e50" } } ], "extra": [ 1, 17, 173, 159, 109, 54, 158, 152, 146, 81, 17, 89, 123, 82, 20, 203, 105, 75, 162, 65, 182, 102, 180, 194, 174, 49, 86, 86, 67, 246, 222, 226, 202, 2, 17, 0, 0, 0, 2, 250, 243, 92, 156, 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