Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: adf2e09e90c41e8f2aed143767bf7b113305217241b9a7752a7884eb21153234

Tx prefix hash: 616b8011a5707d8310a1197c9cb0f2d45465e7e0c0bf2c1c1e1dd00db0a9e0ef
Tx public key: 389e6c39d3f36cdb406e4f51e1cfcfd0d51dd7c092958643ad860fa0dd42119e
Timestamp: 1751382139 Timestamp [UCT]: 2025-07-01 15:02:19 Age [y:d:h:m:s]: 00:214:18:36:59
Block: 1316606 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 151633 RingCT/type: yes/0
Extra: 01389e6c39d3f36cdb406e4f51e1cfcfd0d51dd7c092958643ad860fa0dd42119e021100000004e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f0682b261624e37f7903906f7f798f39ca5db27795de7ff48ba56da8e9a1e64f 0.600000000000 1804267 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": 1316616, "vin": [ { "gen": { "height": 1316606 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f0682b261624e37f7903906f7f798f39ca5db27795de7ff48ba56da8e9a1e64f" } } ], "extra": [ 1, 56, 158, 108, 57, 211, 243, 108, 219, 64, 110, 79, 81, 225, 207, 207, 208, 213, 29, 215, 192, 146, 149, 134, 67, 173, 134, 15, 160, 221, 66, 17, 158, 2, 17, 0, 0, 0, 4, 228, 220, 144, 9, 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