Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4389f671e4e4de1f64c25c5150de964bccd0b85d98a585a03caeaf97f790e5bf

Tx prefix hash: d4c6a13015cb5ddd203ed3bf7d1020a57eb1c98db5d8bb995e91103e5cf81471
Tx public key: d8be705bd203ed7c4371363d0e7aa04ef5a92169b65a7cc56d0a52b3246ff7ac
Timestamp: 1631805251 Timestamp [UCT]: 2021-09-16 15:14:11 Age [y:d:h:m:s]: 03:052:20:06:47
Block: 334979 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 813506 RingCT/type: yes/0
Extra: 01d8be705bd203ed7c4371363d0e7aa04ef5a92169b65a7cc56d0a52b3246ff7ac021100000028fdc024ec000000000000000000

1 output(s) for total of 47.651431939000 dcy

stealth address amount amount idx
00: 0470ef725cac9f8c9ce3e14305c03eb0cf374444bfbd4897710445ca62a6e81f 47.651431939000 690656 of 0

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": 334989, "vin": [ { "gen": { "height": 334979 } } ], "vout": [ { "amount": 47651431939, "target": { "key": "0470ef725cac9f8c9ce3e14305c03eb0cf374444bfbd4897710445ca62a6e81f" } } ], "extra": [ 1, 216, 190, 112, 91, 210, 3, 237, 124, 67, 113, 54, 61, 14, 122, 160, 78, 245, 169, 33, 105, 182, 90, 124, 197, 109, 10, 82, 179, 36, 111, 247, 172, 2, 17, 0, 0, 0, 40, 253, 192, 36, 236, 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