Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 5b086a07651f9a99a7f307999075fe9419f4d6b6fdd5412939caa6b6e1bc1595

Tx prefix hash: eb63ffade8d3b07afa8ca3d7dd765ce9675351dd41020199c9df636a98dfb2b5
Tx public key: 899420f99c1157a102fd8b4e25098aa0f493fc6f4227f2046b9d8304443c2b22
Timestamp: 1703002768 Timestamp [UCT]: 2023-12-19 16:19:28 Age [y:d:h:m:s]: 01:133:06:20:48
Block: 916651 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 356370 RingCT/type: yes/0
Extra: 01899420f99c1157a102fd8b4e25098aa0f493fc6f4227f2046b9d8304443c2b2202110000000175e3f0e9000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4c6be6364ca4d082549fc9300780c83a86e6155b63bf94a42c5dcebde02801d4 0.600000000000 1374209 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": 916661, "vin": [ { "gen": { "height": 916651 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4c6be6364ca4d082549fc9300780c83a86e6155b63bf94a42c5dcebde02801d4" } } ], "extra": [ 1, 137, 148, 32, 249, 156, 17, 87, 161, 2, 253, 139, 78, 37, 9, 138, 160, 244, 147, 252, 111, 66, 39, 242, 4, 107, 157, 131, 4, 68, 60, 43, 34, 2, 17, 0, 0, 0, 1, 117, 227, 240, 233, 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