Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 64aecc04feef7de64761c6636709242505c80d20b830697ff17c4ac7904afe1d

Tx prefix hash: 7d2b8d1e73a6272e8ef306c037c07911621996151828e763ef2b85fd6276cded
Tx public key: 4c917fafa5805fd1ec6cdd4d794f5a00b33c67c5bdc40795b05a7713cfb903b9
Timestamp: 1716778013 Timestamp [UCT]: 2024-05-27 02:46:53 Age [y:d:h:m:s]: 00:311:11:37:15
Block: 1030848 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 222613 RingCT/type: yes/0
Extra: 014c917fafa5805fd1ec6cdd4d794f5a00b33c67c5bdc40795b05a7713cfb903b90211000000057a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0b8fe18cfb2edad349443e0c353a5c79c99bd7257d9ba7e4425cc53514cf06a2 0.600000000000 1499153 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": 1030858, "vin": [ { "gen": { "height": 1030848 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0b8fe18cfb2edad349443e0c353a5c79c99bd7257d9ba7e4425cc53514cf06a2" } } ], "extra": [ 1, 76, 145, 127, 175, 165, 128, 95, 209, 236, 108, 221, 77, 121, 79, 90, 0, 179, 60, 103, 197, 189, 196, 7, 149, 176, 90, 119, 19, 207, 185, 3, 185, 2, 17, 0, 0, 0, 5, 122, 156, 244, 199, 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