Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df85976322fc7da8f91ae7d10a7525823bbecd22af075ad08360979b783bc77c

Tx prefix hash: c85a12e7e1021470d715fb56d9b4a8c5d657d6e629d9f306aaee9b552eeab953
Tx public key: 777bc54158934f79aa741c0639b6da4a8d3b7945b92e8123fbd71e84d2385936
Timestamp: 1748799724 Timestamp [UCT]: 2025-06-01 17:42:04 Age [y:d:h:m:s]: 00:161:01:57:16
Block: 1295774 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 112809 RingCT/type: yes/0
Extra: 01777bc54158934f79aa741c0639b6da4a8d3b7945b92e8123fbd71e84d2385936021100000007bf51b2a2000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 55ac6d88723f1aa98543858b9319fcdd7932862c934138e84c0f2e36c51b7a3f 0.600000000000 1783279 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": 1295784, "vin": [ { "gen": { "height": 1295774 } } ], "vout": [ { "amount": 600000000, "target": { "key": "55ac6d88723f1aa98543858b9319fcdd7932862c934138e84c0f2e36c51b7a3f" } } ], "extra": [ 1, 119, 123, 197, 65, 88, 147, 79, 121, 170, 116, 28, 6, 57, 182, 218, 74, 141, 59, 121, 69, 185, 46, 129, 35, 251, 215, 30, 132, 210, 56, 89, 54, 2, 17, 0, 0, 0, 7, 191, 81, 178, 162, 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