Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: bc1ed453123000e3d3a6c4e8f41c5e083e1fa67d34adb05e32aec7c3d2835584

Tx prefix hash: 26bf7d44eac4c208b819cd6c85ec24e800346d7e20d4d823b9276dc07124e9dc
Tx public key: b3fc0bf530feab87d25977be62ccd70c27d2d1277e453f22079ebaddb7d123c7
Timestamp: 1712684954 Timestamp [UCT]: 2024-04-09 17:49:14 Age [y:d:h:m:s]: 01:002:08:35:14
Block: 996893 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262659 RingCT/type: yes/0
Extra: 01b3fc0bf530feab87d25977be62ccd70c27d2d1277e453f22079ebaddb7d123c7021100000003bfa22221000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de9a3dbb8dfad7c968871528c54d1f31d7d70bd632bd5b700e8e0489d51208df 0.600000000000 1457321 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": 996903, "vin": [ { "gen": { "height": 996893 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de9a3dbb8dfad7c968871528c54d1f31d7d70bd632bd5b700e8e0489d51208df" } } ], "extra": [ 1, 179, 252, 11, 245, 48, 254, 171, 135, 210, 89, 119, 190, 98, 204, 215, 12, 39, 210, 209, 39, 126, 69, 63, 34, 7, 158, 186, 221, 183, 209, 35, 199, 2, 17, 0, 0, 0, 3, 191, 162, 34, 33, 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