Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aec3b8f0d1fd233c57d16c16cdfba17ac1dc746985c04ac0b39441bf08fac459

Tx prefix hash: ecebc711e5bfedf51c1ab40bebc634859dde81aeb48b57ae89c0f3d03f2695eb
Tx public key: 7d646898a2e845f14dcde4f554a6fda4f3b8356b9650d4d7170057b5ee97095e
Timestamp: 1711467191 Timestamp [UCT]: 2024-03-26 15:33:11 Age [y:d:h:m:s]: 01:013:20:04:11
Block: 986838 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 270841 RingCT/type: yes/0
Extra: 017d646898a2e845f14dcde4f554a6fda4f3b8356b9650d4d7170057b5ee97095e02110000000452d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 7cd68afbd5feff9faa86f0195b0bfc4f3e881c6a4d6f44674873ce58aebac778 0.600000000000 1447073 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": 986848, "vin": [ { "gen": { "height": 986838 } } ], "vout": [ { "amount": 600000000, "target": { "key": "7cd68afbd5feff9faa86f0195b0bfc4f3e881c6a4d6f44674873ce58aebac778" } } ], "extra": [ 1, 125, 100, 104, 152, 162, 232, 69, 241, 77, 205, 228, 245, 84, 166, 253, 164, 243, 184, 53, 107, 150, 80, 212, 215, 23, 0, 87, 181, 238, 151, 9, 94, 2, 17, 0, 0, 0, 4, 82, 212, 126, 148, 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