Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 35ab87ceab0bd92a239881df9a0adef1305f511d9aa78989a4c081d416067ef5

Tx prefix hash: eb84565e383a9c9fac29e2ac363806f6fbb0dc90df6ca9b325423af2674bd911
Tx public key: f0364e66c715de65128ac132c058f26b7d52b4c4294735cb68821d2705ec0aa7
Timestamp: 1747670857 Timestamp [UCT]: 2025-05-19 16:07:37 Age [y:d:h:m:s]: 00:141:17:48:06
Block: 1286427 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 98933 RingCT/type: yes/0
Extra: 01f0364e66c715de65128ac132c058f26b7d52b4c4294735cb68821d2705ec0aa70211000000081f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 162378c06af54aa1c4aa1cb92eee078695766ae9d1ae95ff6db6f498d60d151e 0.600000000000 1773892 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": 1286437, "vin": [ { "gen": { "height": 1286427 } } ], "vout": [ { "amount": 600000000, "target": { "key": "162378c06af54aa1c4aa1cb92eee078695766ae9d1ae95ff6db6f498d60d151e" } } ], "extra": [ 1, 240, 54, 78, 102, 199, 21, 222, 101, 18, 138, 193, 50, 192, 88, 242, 107, 125, 82, 180, 196, 41, 71, 53, 203, 104, 130, 29, 39, 5, 236, 10, 167, 2, 17, 0, 0, 0, 8, 31, 144, 81, 122, 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