Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: ef1e54d634f1338cd5059836d0e5c14e40e9d22f73ff333ae0ad31ccaba1d221

Tx prefix hash: 3507997ab3269c84914d5e040665d322789330e794faed5e35e1ac4c866b5c37
Tx public key: ed4bb89e90ffded0f92f3c1d92b23956e61fad0cd6cbc65fb24ca00272e3f234
Timestamp: 1759057470 Timestamp [UCT]: 2025-09-28 11:04:30 Age [y:d:h:m:s]: 00:124:00:12:29
Block: 1378238 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 88622 RingCT/type: yes/0
Extra: 01ed4bb89e90ffded0f92f3c1d92b23956e61fad0cd6cbc65fb24ca00272e3f234021100000004a5dccd79000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 0ec3449789a2a7216aae537d59e09a3de570b0dfaebf025678d4a0e8ff0e42f0 0.600000000000 1866333 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": 1378248, "vin": [ { "gen": { "height": 1378238 } } ], "vout": [ { "amount": 600000000, "target": { "key": "0ec3449789a2a7216aae537d59e09a3de570b0dfaebf025678d4a0e8ff0e42f0" } } ], "extra": [ 1, 237, 75, 184, 158, 144, 255, 222, 208, 249, 47, 60, 29, 146, 178, 57, 86, 230, 31, 173, 12, 214, 203, 198, 95, 178, 76, 160, 2, 114, 227, 242, 52, 2, 17, 0, 0, 0, 4, 165, 220, 205, 121, 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