Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 3351aed677bde572f4c6606b5e0dfee5b62109b3cb8ded1b0482051673f66b45

Tx prefix hash: b818c0fa9dbf4e0a5c3c9c5bc504c4b5e257271b75d6d553efe0edf6a2126aae
Tx public key: 718de8fa57323f43c0b46a77fd67f064a77915c9052adbef34ceff0ea0cbd3a9
Timestamp: 1656901653 Timestamp [UCT]: 2022-07-04 02:27:33 Age [y:d:h:m:s]: 02:296:12:00:57
Block: 536156 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 733054 RingCT/type: yes/0
Extra: 01718de8fa57323f43c0b46a77fd67f064a77915c9052adbef34ceff0ea0cbd3a902110000000e5eb576c5000000000000000000

1 output(s) for total of 10.268163034000 dcy

stealth address amount amount idx
00: b897d3785c9429f54261ae2d25675c0f96ef33f36d945488b86bc8c11f3dad44 10.268163034000 965861 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": 536166, "vin": [ { "gen": { "height": 536156 } } ], "vout": [ { "amount": 10268163034, "target": { "key": "b897d3785c9429f54261ae2d25675c0f96ef33f36d945488b86bc8c11f3dad44" } } ], "extra": [ 1, 113, 141, 232, 250, 87, 50, 63, 67, 192, 180, 106, 119, 253, 103, 240, 100, 167, 121, 21, 201, 5, 42, 219, 239, 52, 206, 255, 14, 160, 203, 211, 169, 2, 17, 0, 0, 0, 14, 94, 181, 118, 197, 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