Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 0ef8855eefc19e7b5865afca209a07bd69b47973b41cfea0916d154b9c940447

Tx prefix hash: c42d227dd06d24098a4c6af0a16a14b4597211c0010f9358f65c3ada71f55b99
Tx public key: bb6c981e99be6e872dc05d945cb47a75de3c7f845152e54118c6413ec439e047
Timestamp: 1752234341 Timestamp [UCT]: 2025-07-11 11:45:41 Age [y:d:h:m:s]: 00:198:17:01:54
Block: 1323244 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 140556 RingCT/type: yes/0
Extra: 01bb6c981e99be6e872dc05d945cb47a75de3c7f845152e54118c6413ec439e047021100000001d8e7d241000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 08420b5f4f364cef56df0a4ff840554d92a6982d6939a882c51a4ffe774cafa9 0.600000000000 1810979 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": 1323254, "vin": [ { "gen": { "height": 1323244 } } ], "vout": [ { "amount": 600000000, "target": { "key": "08420b5f4f364cef56df0a4ff840554d92a6982d6939a882c51a4ffe774cafa9" } } ], "extra": [ 1, 187, 108, 152, 30, 153, 190, 110, 135, 45, 192, 93, 148, 92, 180, 122, 117, 222, 60, 127, 132, 81, 82, 229, 65, 24, 198, 65, 62, 196, 57, 224, 71, 2, 17, 0, 0, 0, 1, 216, 231, 210, 65, 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