Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2af9b68d6a7c330aec9798a9bfc3c4f5da762abd3d7366364d960d011ad3c6d7

Tx prefix hash: ccb13f3351fa9cd507230c46329fb7f05a34b2c311434d631192310c0b5ce44d
Tx public key: 44ccddfd0d8aef944987fc4fbc149ac9f50da256e67b1837d397dffdfb5f322c
Timestamp: 1706430537 Timestamp [UCT]: 2024-01-28 08:28:57 Age [y:d:h:m:s]: 01:068:05:42:45
Block: 945030 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 309854 RingCT/type: yes/0
Extra: 0144ccddfd0d8aef944987fc4fbc149ac9f50da256e67b1837d397dffdfb5f322c02110000000159dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c63b32e1548fb77d9b1682f2fb1cac50b11fccfa5b160d9e52b34d90bd245960 0.600000000000 1403338 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": 945040, "vin": [ { "gen": { "height": 945030 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c63b32e1548fb77d9b1682f2fb1cac50b11fccfa5b160d9e52b34d90bd245960" } } ], "extra": [ 1, 68, 204, 221, 253, 13, 138, 239, 148, 73, 135, 252, 79, 188, 20, 154, 201, 245, 13, 162, 86, 230, 123, 24, 55, 211, 151, 223, 253, 251, 95, 50, 44, 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