Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 00595e564fa9e6e773d1bfa43b110b8865445378bcafb52dfaaea48f6d903337

Tx prefix hash: cc0e48e7424f4dc1c55b53376df6a63b5d8d70bb5328d101e7f75d74c4c6115b
Tx public key: 3948642902badf994c17c2ff1ece17364c811d5250b37de9f90a2e759e7d9a63
Timestamp: 1713091287 Timestamp [UCT]: 2024-04-14 10:41:27 Age [y:d:h:m:s]: 01:203:20:04:48
Block: 1000265 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 404353 RingCT/type: yes/0
Extra: 013948642902badf994c17c2ff1ece17364c811d5250b37de9f90a2e759e7d9a6302110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: e17755cc0cfb9d236fc0ce145741dd5fe8576644e68e805e08bbec333446c581 0.600000000000 1460761 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": 1000275, "vin": [ { "gen": { "height": 1000265 } } ], "vout": [ { "amount": 600000000, "target": { "key": "e17755cc0cfb9d236fc0ce145741dd5fe8576644e68e805e08bbec333446c581" } } ], "extra": [ 1, 57, 72, 100, 41, 2, 186, 223, 153, 76, 23, 194, 255, 30, 206, 23, 54, 76, 129, 29, 82, 80, 179, 125, 233, 249, 10, 46, 117, 158, 125, 154, 99, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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