Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: d24419125931f104b6d316026fc2d16bf69f237e69b511be1d6735a3de387f5f

Tx prefix hash: a4cd87e12d03e49e7a4bbf89a5b33e13dd870c8fc54e2b3aeb1e55eaf225109b
Tx public key: 2199e89a8f3a629135810f84d4a0b0f54328c41563f3fc23d173015e686c6e5b
Timestamp: 1703646520 Timestamp [UCT]: 2023-12-27 03:08:40 Age [y:d:h:m:s]: 00:323:06:20:20
Block: 921977 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 231458 RingCT/type: yes/0
Extra: 012199e89a8f3a629135810f84d4a0b0f54328c41563f3fc23d173015e686c6e5b02110000000752d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bad39965dc68305a0f588a32ea636c5627dadd28ceca7919a6433e5776dd0039 0.600000000000 1379671 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": 921987, "vin": [ { "gen": { "height": 921977 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bad39965dc68305a0f588a32ea636c5627dadd28ceca7919a6433e5776dd0039" } } ], "extra": [ 1, 33, 153, 232, 154, 143, 58, 98, 145, 53, 129, 15, 132, 212, 160, 176, 245, 67, 40, 196, 21, 99, 243, 252, 35, 209, 115, 1, 94, 104, 108, 110, 91, 2, 17, 0, 0, 0, 7, 82, 212, 126, 148, 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