Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 1f214c3a5b14724fad9f334a8943ed9fc4782e45c3c3eda6014b11c412e6fc78

Tx prefix hash: a344c98280c44eb4e61ab4b11829e0f9ac459a40a0ef4c9347471ba2bdfaaa3e
Tx public key: 597c7dc92bcf54f2066e602451fae23f56686ecb8a11d949f7eea44f996bb2cb
Timestamp: 1708308283 Timestamp [UCT]: 2024-02-19 02:04:43 Age [y:d:h:m:s]: 01:122:23:51:00
Block: 960622 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 348816 RingCT/type: yes/0
Extra: 01597c7dc92bcf54f2066e602451fae23f56686ecb8a11d949f7eea44f996bb2cb02110000000252d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 82d8341381d9b2099b4b3e44868ba64013ba8c946fdbb8a6be3de142be89e149 0.600000000000 1420207 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": 960632, "vin": [ { "gen": { "height": 960622 } } ], "vout": [ { "amount": 600000000, "target": { "key": "82d8341381d9b2099b4b3e44868ba64013ba8c946fdbb8a6be3de142be89e149" } } ], "extra": [ 1, 89, 124, 125, 201, 43, 207, 84, 242, 6, 110, 96, 36, 81, 250, 226, 63, 86, 104, 110, 203, 138, 17, 217, 73, 247, 238, 164, 79, 153, 107, 178, 203, 2, 17, 0, 0, 0, 2, 82, 212, 126, 148, 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