Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 95ccdf1f281f19f64d0727b564795c6c05876ea3bd51439610b9a8e2785efded

Tx prefix hash: 85e67b7d112a40447de541ec150bbd82ebc2a521b7dd0e172a9a6fc6a11bcf61
Tx public key: 33c8bc842e2db900d89cb7a3660b0d1da66b31cadf84aed1b3cd3401bde75bc7
Timestamp: 1745558402 Timestamp [UCT]: 2025-04-25 05:20:02 Age [y:d:h:m:s]: 00:258:12:26:34
Block: 1268939 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 182550 RingCT/type: yes/0
Extra: 0133c8bc842e2db900d89cb7a3660b0d1da66b31cadf84aed1b3cd3401bde75bc7021100000001e4dc9009000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: c65ec330dd2ea4e6e26500165df92ee16ec8c1fa0e552678f284995f48dea7c6 0.600000000000 1756172 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": 1268949, "vin": [ { "gen": { "height": 1268939 } } ], "vout": [ { "amount": 600000000, "target": { "key": "c65ec330dd2ea4e6e26500165df92ee16ec8c1fa0e552678f284995f48dea7c6" } } ], "extra": [ 1, 51, 200, 188, 132, 46, 45, 185, 0, 216, 156, 183, 163, 102, 11, 13, 29, 166, 107, 49, 202, 223, 132, 174, 209, 179, 205, 52, 1, 189, 231, 91, 199, 2, 17, 0, 0, 0, 1, 228, 220, 144, 9, 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