Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: c7db78c423d8a487c4bf5b72fc1762a77c724ee28bc3ecfe7d45f3f104157d09

Tx prefix hash: 4986d14efa84b8a46afa62f3e0d94a71e9a7e733573fe763e1edd45293a1fe6c
Tx public key: 67d9144b5a16563a9568a318d439c36082def056df42a91218421c86ba35c7b9
Timestamp: 1725078222 Timestamp [UCT]: 2024-08-31 04:23:42 Age [y:d:h:m:s]: 00:216:04:02:50
Block: 1099653 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 154350 RingCT/type: yes/0
Extra: 0167d9144b5a16563a9568a318d439c36082def056df42a91218421c86ba35c7b902110000000391e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: bcb14b78411c36f096651b00f778f2f4ecf8c8cb35603797c228d7b30b5b7659 0.600000000000 1575618 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": 1099663, "vin": [ { "gen": { "height": 1099653 } } ], "vout": [ { "amount": 600000000, "target": { "key": "bcb14b78411c36f096651b00f778f2f4ecf8c8cb35603797c228d7b30b5b7659" } } ], "extra": [ 1, 103, 217, 20, 75, 90, 22, 86, 58, 149, 104, 163, 24, 212, 57, 195, 96, 130, 222, 240, 86, 223, 66, 169, 18, 24, 66, 28, 134, 186, 53, 199, 185, 2, 17, 0, 0, 0, 3, 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