Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 233276cc2507edf6562be917d3c65fd345c3835d809b63058e936dc55b905534

Tx prefix hash: 2a361372823649f84f5f4988f57b103d52d2798d14023fbf9b1f213459894b61
Tx public key: 1c6b6e42e4d28b2d180b48ba85aa765ca6f3b06657387ec1a2d059710e5d0f75
Timestamp: 1747268300 Timestamp [UCT]: 2025-05-15 00:18:20 Age [y:d:h:m:s]: 00:179:19:26:24
Block: 1283094 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 126203 RingCT/type: yes/0
Extra: 011c6b6e42e4d28b2d180b48ba85aa765ca6f3b06657387ec1a2d059710e5d0f7502110000000125a35a0f000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: ef9c39960258d6aa795a63a0f6117d803540daac3af5d69adf187b32f5356054 0.600000000000 1770511 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": 1283104, "vin": [ { "gen": { "height": 1283094 } } ], "vout": [ { "amount": 600000000, "target": { "key": "ef9c39960258d6aa795a63a0f6117d803540daac3af5d69adf187b32f5356054" } } ], "extra": [ 1, 28, 107, 110, 66, 228, 210, 139, 45, 24, 11, 72, 186, 133, 170, 118, 92, 166, 243, 176, 102, 87, 56, 126, 193, 162, 208, 89, 113, 14, 93, 15, 117, 2, 17, 0, 0, 0, 1, 37, 163, 90, 15, 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