Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: be4a421ae28df42d02751f536504b031621435d8ca09afd7a83f9d86c80b0d06

Tx prefix hash: 42ec612ff63a28d4b44b271f495da3b415dc313bd26ae8bd80fcb60b590fd983
Tx public key: f74427f5d9eda58506bc9eefaa01c27754728cb118c71a3d05340ab67e268cc4
Timestamp: 1658538872 Timestamp [UCT]: 2022-07-23 01:14:32 Age [y:d:h:m:s]: 02:235:17:50:17
Block: 549634 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 689686 RingCT/type: yes/0
Extra: 01f74427f5d9eda58506bc9eefaa01c27754728cb118c71a3d05340ab67e268cc40211000000015eb576c5000000000000000000

1 output(s) for total of 9.264767537000 dcy

stealth address amount amount idx
00: 29afbd5d1d476b76849d7faf1eae696af1ff11c081e9f42ee13b77c5946e37be 9.264767537000 981023 of 0

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": 549644, "vin": [ { "gen": { "height": 549634 } } ], "vout": [ { "amount": 9264767537, "target": { "key": "29afbd5d1d476b76849d7faf1eae696af1ff11c081e9f42ee13b77c5946e37be" } } ], "extra": [ 1, 247, 68, 39, 245, 217, 237, 165, 133, 6, 188, 158, 239, 170, 1, 194, 119, 84, 114, 140, 177, 24, 199, 26, 61, 5, 52, 10, 182, 126, 38, 140, 196, 2, 17, 0, 0, 0, 1, 94, 181, 118, 197, 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