Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 61ee5d1cdf76f4e602b9c65d9cf47f581cbdbc6ed818ff3793640eef89e378c9

Tx prefix hash: a878aa3e61d9108fbacb506dc48cf684b422654561873d6eb7a162d49d1ec4fd
Tx public key: e936cea168a23261aa3badf2dbf3b5337fe02e9b8b271105e2d6856afca3dc28
Timestamp: 1708761936 Timestamp [UCT]: 2024-02-24 08:05:36 Age [y:d:h:m:s]: 01:039:22:01:37
Block: 964389 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 289545 RingCT/type: yes/0
Extra: 01e936cea168a23261aa3badf2dbf3b5337fe02e9b8b271105e2d6856afca3dc280211000000010011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 338bb1420bcf7ef26a5ad323934c765cb96ba2f22c61a405e925fa925db8131d 0.600000000000 1424120 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": 964399, "vin": [ { "gen": { "height": 964389 } } ], "vout": [ { "amount": 600000000, "target": { "key": "338bb1420bcf7ef26a5ad323934c765cb96ba2f22c61a405e925fa925db8131d" } } ], "extra": [ 1, 233, 54, 206, 161, 104, 162, 50, 97, 170, 59, 173, 242, 219, 243, 181, 51, 127, 224, 46, 155, 139, 39, 17, 5, 226, 214, 133, 106, 252, 163, 220, 40, 2, 17, 0, 0, 0, 1, 0, 17, 5, 91, 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