Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 9d38036185bf3ba4eb1472ac9b99ba2b3c80d839f7de63f9ad1887425cd7436d

Tx prefix hash: a2a1d9ebf0550583a04c4579381dd2892d5fef76494a346cb6313915004b32e9
Tx public key: c9a6a89244d3e026b6457c027c610b851cdcc66b3a3b47c497be1685a94a6fc4
Timestamp: 1705782420 Timestamp [UCT]: 2024-01-20 20:27:00 Age [y:d:h:m:s]: 01:087:15:30:11
Block: 939651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 323752 RingCT/type: yes/0
Extra: 01c9a6a89244d3e026b6457c027c610b851cdcc66b3a3b47c497be1685a94a6fc40211000000070011055b000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 405178bda0601550ae3fe5dc71be6a64318f3ba6cec64a881b4a6351d410b681 0.600000000000 1397761 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": 939661, "vin": [ { "gen": { "height": 939651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "405178bda0601550ae3fe5dc71be6a64318f3ba6cec64a881b4a6351d410b681" } } ], "extra": [ 1, 201, 166, 168, 146, 68, 211, 224, 38, 182, 69, 124, 2, 124, 97, 11, 133, 28, 220, 198, 107, 58, 59, 71, 196, 151, 190, 22, 133, 169, 74, 111, 196, 2, 17, 0, 0, 0, 7, 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