Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: df6a791257e0d39181996ec43b7bdda577dcda176bf592270e699d19001bba9b

Tx prefix hash: f4cc3b2332ef9cbaa12cf5bf9f6e311eb8ec65fe96dbe5a68db6218ef254a034
Tx public key: 3665f8b69b10791c386ec5f62d308b923be59141ee0adea5e3de64c5226713dc
Timestamp: 1633181375 Timestamp [UCT]: 2021-10-02 13:29:35 Age [y:d:h:m:s]: 03:207:03:07:54
Block: 345204 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 924788 RingCT/type: yes/0
Extra: 013665f8b69b10791c386ec5f62d308b923be59141ee0adea5e3de64c5226713dc02110000000af29d7abf000000000000000000

1 output(s) for total of 44.076161191000 dcy

stealth address amount amount idx
00: afe02de83b230483f0c6a791f1a209bd9dc289cb4ab61856b3bdc7524f99af62 44.076161191000 708144 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": 345214, "vin": [ { "gen": { "height": 345204 } } ], "vout": [ { "amount": 44076161191, "target": { "key": "afe02de83b230483f0c6a791f1a209bd9dc289cb4ab61856b3bdc7524f99af62" } } ], "extra": [ 1, 54, 101, 248, 182, 155, 16, 121, 28, 56, 110, 197, 246, 45, 48, 139, 146, 59, 229, 145, 65, 238, 10, 222, 165, 227, 222, 100, 197, 34, 103, 19, 220, 2, 17, 0, 0, 0, 10, 242, 157, 122, 191, 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