Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4eca43d7cec26f7702e68a187259d1f6102ae79899b348a92578d77579253de8

Tx prefix hash: b42111b854e3e35cf4e5bb770c739238dc237ea1bda4b0953e6206ef892b8e22
Tx public key: 85a3860163a7b5dfb9851003f10fce894b9f909da65b6f53640a3e61efea5e38
Timestamp: 1711448938 Timestamp [UCT]: 2024-03-26 10:28:58 Age [y:d:h:m:s]: 01:250:14:03:10
Block: 986684 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 437791 RingCT/type: yes/0
Extra: 0185a3860163a7b5dfb9851003f10fce894b9f909da65b6f53640a3e61efea5e3802110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 07d83a9ee4a0531b92659ce3faabba49a67f0de7b82f50d5690406900fbacf7f 0.600000000000 1446917 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": 986694, "vin": [ { "gen": { "height": 986684 } } ], "vout": [ { "amount": 600000000, "target": { "key": "07d83a9ee4a0531b92659ce3faabba49a67f0de7b82f50d5690406900fbacf7f" } } ], "extra": [ 1, 133, 163, 134, 1, 99, 167, 181, 223, 185, 133, 16, 3, 241, 15, 206, 137, 75, 159, 144, 157, 166, 91, 111, 83, 100, 10, 62, 97, 239, 234, 94, 56, 2, 17, 0, 0, 0, 1, 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