Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 90b928bae60aaaa6b02924f996a1a0291f5f9adf0d8c3a083ef00e61ca4e9ebf

Tx prefix hash: ed21d680b97919777a0e706eb9e48db79d7a508f8d741b41503169750bd75899
Tx public key: 52b0e095227086c2668e7cf9d577505f11813a87c7cd0587fb55cae278dbbb83
Timestamp: 1699752495 Timestamp [UCT]: 2023-11-12 01:28:15 Age [y:d:h:m:s]: 01:107:04:38:17
Block: 889701 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 337756 RingCT/type: yes/0
Extra: 0152b0e095227086c2668e7cf9d577505f11813a87c7cd0587fb55cae278dbbb830211000000074b8f5122000000000000000000

1 output(s) for total of 0.691912622000 dcy

stealth address amount amount idx
00: 64f2a9af38ddbfac5bc71f12959f1c5680b2179aa9718dd9e17dae73147f3dc4 0.691912622000 1345710 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": 889711, "vin": [ { "gen": { "height": 889701 } } ], "vout": [ { "amount": 691912622, "target": { "key": "64f2a9af38ddbfac5bc71f12959f1c5680b2179aa9718dd9e17dae73147f3dc4" } } ], "extra": [ 1, 82, 176, 224, 149, 34, 112, 134, 194, 102, 142, 124, 249, 213, 119, 80, 95, 17, 129, 58, 135, 199, 205, 5, 135, 251, 85, 202, 226, 120, 219, 187, 131, 2, 17, 0, 0, 0, 7, 75, 143, 81, 34, 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