Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 05f4ec3934c1a6065b799512eebb460112047da3a9c09f83a57441bfbe1c0c2d

Tx prefix hash: 224d6ad44a6c988f4d262fdc3587aab0821233453141803faf042eb85ac5dfa6
Tx public key: 5fb1e2e8b711764d1d4f1d87c04ee9ee9582267022a3d98f027436ade5fc3a9a
Timestamp: 1603730452 Timestamp [UCT]: 2020-10-26 16:40:52 Age [y:d:h:m:s]: 04:081:10:29:33
Block: 144701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1052904 RingCT/type: yes/0
Extra: 015fb1e2e8b711764d1d4f1d87c04ee9ee9582267022a3d98f027436ade5fc3a9a021100000004508974f9000000000000000000

1 output(s) for total of 203.507763814000 dcy

stealth address amount amount idx
00: 9fce8de254f7fd153467c16a9e8074343fd5a6423d051b2d0e9e7a5feb37666e 203.507763814000 240371 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": 144711, "vin": [ { "gen": { "height": 144701 } } ], "vout": [ { "amount": 203507763814, "target": { "key": "9fce8de254f7fd153467c16a9e8074343fd5a6423d051b2d0e9e7a5feb37666e" } } ], "extra": [ 1, 95, 177, 226, 232, 183, 17, 118, 77, 29, 79, 29, 135, 192, 78, 233, 238, 149, 130, 38, 112, 34, 163, 217, 143, 2, 116, 54, 173, 229, 252, 58, 154, 2, 17, 0, 0, 0, 4, 80, 137, 116, 249, 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