Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 4c3424d855dbe00164256bc5107f8ac217070c38685bff7096530c68662eafb9

Tx prefix hash: df0ab56d1139e60d7b8151fd450550819f18e8387aa6563459db7e95b80aa56a
Tx public key: 2a2939db269b704dce529cc8ee707f87b7b80b4d8b0f37f895631b3f58f3dd54
Timestamp: 1747455673 Timestamp [UCT]: 2025-05-17 04:21:13 Age [y:d:h:m:s]: 00:180:19:37:02
Block: 1284641 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126937 RingCT/type: yes/0
Extra: 012a2939db269b704dce529cc8ee707f87b7b80b4d8b0f37f895631b3f58f3dd540211000000031f90517a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 4a773a4e15d81d6722fd003087ccd51fb096ebd6f74c9119b6751bf310848afe 0.600000000000 1772098 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": 1284651, "vin": [ { "gen": { "height": 1284641 } } ], "vout": [ { "amount": 600000000, "target": { "key": "4a773a4e15d81d6722fd003087ccd51fb096ebd6f74c9119b6751bf310848afe" } } ], "extra": [ 1, 42, 41, 57, 219, 38, 155, 112, 77, 206, 82, 156, 200, 238, 112, 127, 135, 183, 184, 11, 77, 139, 15, 55, 248, 149, 99, 27, 63, 88, 243, 221, 84, 2, 17, 0, 0, 0, 3, 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