Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: aa2c40b116a5c5bf760c177f59f0063c91db2e689ed5e137618168d0d1670c13

Tx prefix hash: f44c35592030e6bec508fdaa94911c3ac6f6cbdeeb5a9136d7f9bd7a1e6e7d3a
Tx public key: 8d2e9939eaa971ac792666c193e9cd56ef57895243564ae625219a2b213d7cf0
Timestamp: 1733742259 Timestamp [UCT]: 2024-12-09 11:04:19 Age [y:d:h:m:s]: 00:191:07:26:09
Block: 1171387 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 136440 RingCT/type: yes/0
Extra: 018d2e9939eaa971ac792666c193e9cd56ef57895243564ae625219a2b213d7cf00211000000041f0a53eb000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 5a2cace3a1a597dd747419d110d4d8104dc956219624f53c37625d2663569abd 0.600000000000 1657136 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": 1171397, "vin": [ { "gen": { "height": 1171387 } } ], "vout": [ { "amount": 600000000, "target": { "key": "5a2cace3a1a597dd747419d110d4d8104dc956219624f53c37625d2663569abd" } } ], "extra": [ 1, 141, 46, 153, 57, 234, 169, 113, 172, 121, 38, 102, 193, 147, 233, 205, 86, 239, 87, 137, 82, 67, 86, 74, 230, 37, 33, 154, 43, 33, 61, 124, 240, 2, 17, 0, 0, 0, 4, 31, 10, 83, 235, 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