Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f2b5a8fcdf5f36934ce308043fedb171a4cd4a901fc10aaa1915651abc627270

Tx prefix hash: d24d6312858d82f4f82879ead9e669df81c6d019247af071cb3afebbd4822177
Tx public key: bb843c68567533e8a4ba1b63dcdd929666f370212c75c5ccf711461a45b8ecc1
Timestamp: 1731879621 Timestamp [UCT]: 2024-11-17 21:40:21 Age [y:d:h:m:s]: 00:187:07:01:02
Block: 1155957 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 133709 RingCT/type: yes/0
Extra: 01bb843c68567533e8a4ba1b63dcdd929666f370212c75c5ccf711461a45b8ecc1021100000001a11dba98000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 8e5d80194e952e8118f8aa3c5a1f562d9df84c50015f77e8300ad137f5b8c052 0.600000000000 1641576 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": 1155967, "vin": [ { "gen": { "height": 1155957 } } ], "vout": [ { "amount": 600000000, "target": { "key": "8e5d80194e952e8118f8aa3c5a1f562d9df84c50015f77e8300ad137f5b8c052" } } ], "extra": [ 1, 187, 132, 60, 104, 86, 117, 51, 232, 164, 186, 27, 99, 220, 221, 146, 150, 102, 243, 112, 33, 44, 117, 197, 204, 247, 17, 70, 26, 69, 184, 236, 193, 2, 17, 0, 0, 0, 1, 161, 29, 186, 152, 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