Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2d25ed85be90beebae8b0747a88fdf97c0a7f4aec18e879a735de786c210fb43

Tx prefix hash: 5b44a3e21ec9cfd049b1da65d59832bc0e107f03d0a95a2eda42ad5209d56271
Tx public key: 32b6378dad8c3c0e513f73e90a33d4650f0edce8fd051d60c5e409e143fcdc16
Timestamp: 1723600716 Timestamp [UCT]: 2024-08-14 01:58:36 Age [y:d:h:m:s]: 01:086:00:52:16
Block: 1087409 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 319952 RingCT/type: yes/0
Extra: 0132b6378dad8c3c0e513f73e90a33d4650f0edce8fd051d60c5e409e143fcdc1602110000000ae914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 67256ace7e6925762730c953872d2e619f93066358679d86dad314147a258675 0.600000000000 1562018 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": 1087419, "vin": [ { "gen": { "height": 1087409 } } ], "vout": [ { "amount": 600000000, "target": { "key": "67256ace7e6925762730c953872d2e619f93066358679d86dad314147a258675" } } ], "extra": [ 1, 50, 182, 55, 141, 173, 140, 60, 14, 81, 63, 115, 233, 10, 51, 212, 101, 15, 14, 220, 232, 253, 5, 29, 96, 197, 228, 9, 225, 67, 252, 220, 22, 2, 17, 0, 0, 0, 10, 233, 20, 221, 21, 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