Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 866c7e473bdff662dc31610c1d834ff4d8464495a94d63277de3a120b21ae363

Tx prefix hash: d5b9ca0bc9f3a701a8c807d93b34e10e2412af752069812e12d34ff7f6f93122
Tx public key: b969fbaa46c0e449b6c57c1f8ed601517e3c5a562a93ddcf920fbb85b65df3e1
Timestamp: 1696723861 Timestamp [UCT]: 2023-10-08 00:11:01 Age [y:d:h:m:s]: 01:144:18:01:32
Block: 864792 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 364459 RingCT/type: yes/0
Extra: 01b969fbaa46c0e449b6c57c1f8ed601517e3c5a562a93ddcf920fbb85b65df3e1021100000005bfa22221000000000000000000

1 output(s) for total of 0.836729627000 dcy

stealth address amount amount idx
00: 23f9e1a6c5b0a2e001c24429eb383c29d2eb4cae83be5c7f7b00ba9d898dca4f 0.836729627000 1319312 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": 864802, "vin": [ { "gen": { "height": 864792 } } ], "vout": [ { "amount": 836729627, "target": { "key": "23f9e1a6c5b0a2e001c24429eb383c29d2eb4cae83be5c7f7b00ba9d898dca4f" } } ], "extra": [ 1, 185, 105, 251, 170, 70, 192, 228, 73, 182, 197, 124, 31, 142, 214, 1, 81, 126, 60, 90, 86, 42, 147, 221, 207, 146, 15, 187, 133, 182, 93, 243, 225, 2, 17, 0, 0, 0, 5, 191, 162, 34, 33, 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