Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 21a527523859dc3bb5881b2fa3a6bdf2f9081d133910abf6c402a5b93cfdb600

Tx prefix hash: 8656017c34e26fa5cebbce599c8a84aeea9bb0637e346ef26d8c873a9110e9f4
Tx public key: 9ac7869c65adb5ff5dd700d12fff00f4c390f6b66bfc52092d15d08b202fcca0
Timestamp: 1671741538 Timestamp [UCT]: 2022-12-22 20:38:58 Age [y:d:h:m:s]: 02:106:17:19:13
Block: 658353 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 597958 RingCT/type: yes/0
Extra: 019ac7869c65adb5ff5dd700d12fff00f4c390f6b66bfc52092d15d08b202fcca0021100000001e6d27f9c000000000000000000

1 output(s) for total of 4.042064040000 dcy

stealth address amount amount idx
00: cc62e283c35ea7955bf02e231c8ec23fe0965f406e0c81efceac3ae41169f247 4.042064040000 1099026 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": 658363, "vin": [ { "gen": { "height": 658353 } } ], "vout": [ { "amount": 4042064040, "target": { "key": "cc62e283c35ea7955bf02e231c8ec23fe0965f406e0c81efceac3ae41169f247" } } ], "extra": [ 1, 154, 199, 134, 156, 101, 173, 181, 255, 93, 215, 0, 209, 47, 255, 0, 244, 195, 144, 246, 182, 107, 252, 82, 9, 45, 21, 208, 139, 32, 47, 204, 160, 2, 17, 0, 0, 0, 1, 230, 210, 127, 156, 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