Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 2094093c73dde51c304e22972f987c72425f48c93d5ecd9edc2f80eee422da8b

Tx prefix hash: bd9c3a32076eac14f5980f6989c4b0fd75e2edbb8b41aef0772ca323e75f1259
Tx public key: b7eb2541b60728a3cc6ad97977d2a30cbe7f309d83074598e8d023a50420f16c
Timestamp: 1717779001 Timestamp [UCT]: 2024-06-07 16:50:01 Age [y:d:h:m:s]: 00:282:10:06:22
Block: 1039151 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 201823 RingCT/type: yes/0
Extra: 01b7eb2541b60728a3cc6ad97977d2a30cbe7f309d83074598e8d023a50420f16c02110000000359dad3f5000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: f7db33c7bbb8a1e16286d09696beb090b04c7c2bc904f57811be3f7c57161713 0.600000000000 1507766 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": 1039161, "vin": [ { "gen": { "height": 1039151 } } ], "vout": [ { "amount": 600000000, "target": { "key": "f7db33c7bbb8a1e16286d09696beb090b04c7c2bc904f57811be3f7c57161713" } } ], "extra": [ 1, 183, 235, 37, 65, 182, 7, 40, 163, 204, 106, 217, 121, 119, 210, 163, 12, 190, 127, 48, 157, 131, 7, 69, 152, 232, 208, 35, 165, 4, 32, 241, 108, 2, 17, 0, 0, 0, 3, 89, 218, 211, 245, 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