Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 768d33178ebc53abe02dc24ea104e62513b469d47bbd2da7636f79c207aaad6e

Tx prefix hash: 200f18911eceee9de56d061716ef68bd990d8f5ace9bc0dfaa58c4be89fe706b
Tx public key: 6d592a7d0bf586a7e72d772e66b54b75d3d69910a91f31851ad8ed5d0cd1af9a
Timestamp: 1711944657 Timestamp [UCT]: 2024-04-01 04:10:57 Age [y:d:h:m:s]: 01:002:10:13:53
Block: 990747 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 262715 RingCT/type: yes/0
Extra: 016d592a7d0bf586a7e72d772e66b54b75d3d69910a91f31851ad8ed5d0cd1af9a02110000000352d47e94000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 3d7b5292b6a139a67d0bcb0a7ffa0926a9730a8a37339665858700acd968a1f9 0.600000000000 1451075 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": 990757, "vin": [ { "gen": { "height": 990747 } } ], "vout": [ { "amount": 600000000, "target": { "key": "3d7b5292b6a139a67d0bcb0a7ffa0926a9730a8a37339665858700acd968a1f9" } } ], "extra": [ 1, 109, 89, 42, 125, 11, 245, 134, 167, 231, 45, 119, 46, 102, 181, 75, 117, 211, 214, 153, 16, 169, 31, 49, 133, 26, 216, 237, 93, 12, 209, 175, 154, 2, 17, 0, 0, 0, 3, 82, 212, 126, 148, 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