Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6ab795ec92bcc6a5a71278e70a4ede199ca940f9589a54bd84cbb4ef08232fa0

Tx prefix hash: 00f4b1f89bc024ab91b22c25ab11e57f6f0bfa3d6a77e88b3bae42086a0bbfc8
Tx public key: 58d1137d9b217fe51293804d8c83d6dadf82b601ee30b79fbdc8f8200989f6c7
Timestamp: 1632288279 Timestamp [UCT]: 2021-09-22 05:24:39 Age [y:d:h:m:s]: 03:108:14:44:45
Block: 338587 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 853807 RingCT/type: yes/0
Extra: 0158d1137d9b217fe51293804d8c83d6dadf82b601ee30b79fbdc8f8200989f6c70211000000228d0de867000000000000000000

1 output(s) for total of 46.357621908000 dcy

stealth address amount amount idx
00: 5c70788a9ddee665006015a94c11a5e7ea32c6e03d6dc99fa7eddacad6595557 46.357621908000 696772 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": 338597, "vin": [ { "gen": { "height": 338587 } } ], "vout": [ { "amount": 46357621908, "target": { "key": "5c70788a9ddee665006015a94c11a5e7ea32c6e03d6dc99fa7eddacad6595557" } } ], "extra": [ 1, 88, 209, 19, 125, 155, 33, 127, 229, 18, 147, 128, 77, 140, 131, 214, 218, 223, 130, 182, 1, 238, 48, 183, 159, 189, 200, 248, 32, 9, 137, 246, 199, 2, 17, 0, 0, 0, 34, 141, 13, 232, 103, 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