Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: e2113e6361ea059865eb12f524eac9c246d4bdf6b14439f281c79046fe851e6e

Tx prefix hash: 3875d9be71e6ea08e8382ea7cc29bf754a08ae4e8b4aa4738eb624dd79e2dd1d
Tx public key: 22848db5659be1b2cc6d6a7ed1e716cc34302c834e8451ab6116c5be9be5fbf7
Timestamp: 1713527078 Timestamp [UCT]: 2024-04-19 11:44:38 Age [y:d:h:m:s]: 01:198:20:02:11
Block: 1003883 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 400763 RingCT/type: yes/0
Extra: 0122848db5659be1b2cc6d6a7ed1e716cc34302c834e8451ab6116c5be9be5fbf702110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: beec523cc42de06165bd3e72fd7f283e8e8b7e834f80768dfaa49b204990db11 0.600000000000 1464431 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": 1003893, "vin": [ { "gen": { "height": 1003883 } } ], "vout": [ { "amount": 600000000, "target": { "key": "beec523cc42de06165bd3e72fd7f283e8e8b7e834f80768dfaa49b204990db11" } } ], "extra": [ 1, 34, 132, 141, 181, 101, 155, 225, 178, 204, 109, 106, 126, 209, 231, 22, 204, 52, 48, 44, 131, 78, 132, 81, 171, 97, 22, 197, 190, 155, 229, 251, 247, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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