Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 04d1c092dbb875059727c56053afd4e37fa83d1eb96f30c118b0423e7d63b5b7

Tx prefix hash: 8c827df65e0c0241295a5dd0846dfac39db150952d8f5c60f450074d1bf1946d
Tx public key: ee6813b6a7e4e99b59e80f9682385c34828b0408e227400d8e2d86815b76108f
Timestamp: 1709047119 Timestamp [UCT]: 2024-02-27 15:18:39 Age [y:d:h:m:s]: 00:344:02:51:01
Block: 966757 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 246053 RingCT/type: yes/0
Extra: 01ee6813b6a7e4e99b59e80f9682385c34828b0408e227400d8e2d86815b76108f0211000000047a9cf4c7000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 53cd9620d35972e83ed2822f9c3b7dd07d0ff9c3ac9d2420664c6c2014b29b9a 0.600000000000 1426528 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": 966767, "vin": [ { "gen": { "height": 966757 } } ], "vout": [ { "amount": 600000000, "target": { "key": "53cd9620d35972e83ed2822f9c3b7dd07d0ff9c3ac9d2420664c6c2014b29b9a" } } ], "extra": [ 1, 238, 104, 19, 182, 167, 228, 233, 155, 89, 232, 15, 150, 130, 56, 92, 52, 130, 139, 4, 8, 226, 39, 64, 13, 142, 45, 134, 129, 91, 118, 16, 143, 2, 17, 0, 0, 0, 4, 122, 156, 244, 199, 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