Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 55a6d62c320057f2560b85b25712c653122671aa63235af2bb4eb3f17a607f6a

Tx prefix hash: e0d84bcb76a08a96ea658dc9c4b5f0858ecafb7b673f3556e426596e211df93c
Tx public key: e968f56e65f7327bc527286d9700c2c170884ce99fe89a7b2114502a843cba9c
Timestamp: 1714570036 Timestamp [UCT]: 2024-05-01 13:27:16 Age [y:d:h:m:s]: 00:324:04:20:35
Block: 1012539 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231735 RingCT/type: yes/0
Extra: 01e968f56e65f7327bc527286d9700c2c170884ce99fe89a7b2114502a843cba9c0211000000027a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 601adaa48fa9c98a554de89f49bddb5d77c9343fbd9d063505f3a8206e0f40c1 0.600000000000 1475101 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": 1012549, "vin": [ { "gen": { "height": 1012539 } } ], "vout": [ { "amount": 600000000, "target": { "key": "601adaa48fa9c98a554de89f49bddb5d77c9343fbd9d063505f3a8206e0f40c1" } } ], "extra": [ 1, 233, 104, 245, 110, 101, 247, 50, 123, 197, 39, 40, 109, 151, 0, 194, 193, 112, 136, 76, 233, 159, 232, 154, 123, 33, 20, 80, 42, 132, 60, 186, 156, 2, 17, 0, 0, 0, 2, 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