Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 935490fe9c9def87d74841cd72391467b669747438f79c0490f18df70689cf34

Tx prefix hash: 453938f65df352eeab8290ea5d5a4833f3530f660e028f67d2feb1e101b042e8
Tx public key: 8bc8d05dc103dbfeb05f017ba202a2d69a174f9c7f48b6be362d77c28715f26c
Timestamp: 1656937377 Timestamp [UCT]: 2022-07-04 12:22:57 Age [y:d:h:m:s]: 02:259:04:53:21
Block: 536456 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 706387 RingCT/type: yes/0
Extra: 018bc8d05dc103dbfeb05f017ba202a2d69a174f9c7f48b6be362d77c28715f26c0211000000012e6b1fd5000000000000000000

1 output(s) for total of 10.244687860000 dcy

stealth address amount amount idx
00: 65dd3480e0e12c31149fda3c14af0f843615e75452f3045213995fd488c49b37 10.244687860000 966223 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": 536466, "vin": [ { "gen": { "height": 536456 } } ], "vout": [ { "amount": 10244687860, "target": { "key": "65dd3480e0e12c31149fda3c14af0f843615e75452f3045213995fd488c49b37" } } ], "extra": [ 1, 139, 200, 208, 93, 193, 3, 219, 254, 176, 95, 1, 123, 162, 2, 162, 214, 154, 23, 79, 156, 127, 72, 182, 190, 54, 45, 119, 194, 135, 21, 242, 108, 2, 17, 0, 0, 0, 1, 46, 107, 31, 213, 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