Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 08803352d32a5b3fedc33b761374db03ada4dfbde14f7455dc83503c84f3b232

Tx prefix hash: 36acc9dede2703684360801ec3ec0ac73a79243865e0d9b2f02754a01a118f77
Tx public key: 7e7620d2fd773f6186c123059d27e8a0cfe55c20aeb73c523a9739a6279d5bd5
Timestamp: 1722269269 Timestamp [UCT]: 2024-07-29 16:07:49 Age [y:d:h:m:s]: 00:262:22:39:06
Block: 1076365 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 187847 RingCT/type: yes/0
Extra: 017e7620d2fd773f6186c123059d27e8a0cfe55c20aeb73c523a9739a6279d5bd502110000000991e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 641c6ccd23161b865bcabd510a7c8ae97fda3e8b1553415aa92fcd90c28d343f 0.600000000000 1548902 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": 1076375, "vin": [ { "gen": { "height": 1076365 } } ], "vout": [ { "amount": 600000000, "target": { "key": "641c6ccd23161b865bcabd510a7c8ae97fda3e8b1553415aa92fcd90c28d343f" } } ], "extra": [ 1, 126, 118, 32, 210, 253, 119, 63, 97, 134, 193, 35, 5, 157, 39, 232, 160, 207, 229, 92, 32, 174, 183, 60, 82, 58, 151, 57, 166, 39, 157, 91, 213, 2, 17, 0, 0, 0, 9, 145, 225, 60, 4, 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