Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f7b8a95eae2827602721293ecae793e075ef1f708b1a09a47eb1792d0761d3c8

Tx prefix hash: 2dbd6514ef0a8952025e07a0ce18e0c6ec41ee5d96c2ba09129d5fa2dba66027
Tx public key: 26532fe5c613907f95ad7d65b753b0462c42f96852f7f24ed2e7ec228a941ff4
Timestamp: 1732880483 Timestamp [UCT]: 2024-11-29 11:41:23 Age [y:d:h:m:s]: 00:127:00:36:52
Block: 1164238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 90604 RingCT/type: yes/0
Extra: 0126532fe5c613907f95ad7d65b753b0462c42f96852f7f24ed2e7ec228a941ff40211000000011f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 678b5fec642ebeb589b28e61dcf5eaf83223cdd1f11b532b97c4a59f1af4cc8f 0.600000000000 1649911 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": 1164248, "vin": [ { "gen": { "height": 1164238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "678b5fec642ebeb589b28e61dcf5eaf83223cdd1f11b532b97c4a59f1af4cc8f" } } ], "extra": [ 1, 38, 83, 47, 229, 198, 19, 144, 127, 149, 173, 125, 101, 183, 83, 176, 70, 44, 66, 249, 104, 82, 247, 242, 78, 210, 231, 236, 34, 138, 148, 31, 244, 2, 17, 0, 0, 0, 1, 31, 10, 83, 235, 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