Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 24394b63060c12e8efc1d949b9c04d4cef954c6d3da0db17ba8ab758dff5a5cd

Tx prefix hash: 8783cf30c68ec55bd95e8dba5c30514d7a7bab4b3dd74f26692a19059baa7604
Tx public key: af5f928f50888cace4dfa918e15a599d4400f1ff7b4e760108cf1df79fddc136
Timestamp: 1648457425 Timestamp [UCT]: 2022-03-28 08:50:25 Age [y:d:h:m:s]: 03:218:10:23:47
Block: 468103 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 934027 RingCT/type: yes/0
Extra: 01af5f928f50888cace4dfa918e15a599d4400f1ff7b4e760108cf1df79fddc136021100000008c9067537000000000000000000

1 output(s) for total of 17.257611756000 dcy

stealth address amount amount idx
00: 44bcb73ad04016aaea3c602aa388debbb822219d4220a6cd62a6f22e78e68979 17.257611756000 886749 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": 468113, "vin": [ { "gen": { "height": 468103 } } ], "vout": [ { "amount": 17257611756, "target": { "key": "44bcb73ad04016aaea3c602aa388debbb822219d4220a6cd62a6f22e78e68979" } } ], "extra": [ 1, 175, 95, 146, 143, 80, 136, 140, 172, 228, 223, 169, 24, 225, 90, 89, 157, 68, 0, 241, 255, 123, 78, 118, 1, 8, 207, 29, 247, 159, 221, 193, 54, 2, 17, 0, 0, 0, 8, 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