Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: f6acea786217e3ae0f828d5ebfdd7a67cd7eb7c334f1da19355cc83de9bffece

Tx prefix hash: b83d59b0ee219280ec1ce109c27c9bf64b0bec163ec5da2d713d047fe8b88a38
Tx public key: 05f4ea9dd747c406e532fa56aacf7ba953da292703ef6589ea8dc6aa3b3ce2a1
Timestamp: 1634934490 Timestamp [UCT]: 2021-10-22 20:28:10 Age [y:d:h:m:s]: 03:034:13:14:36
Block: 358334 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 802984 RingCT/type: yes/0
Extra: 0105f4ea9dd747c406e532fa56aacf7ba953da292703ef6589ea8dc6aa3b3ce2a102110000000494fe4942000000000000000000

1 output(s) for total of 39.874120581000 dcy

stealth address amount amount idx
00: e392df9a8badf9d3a4a06ad57c616923a547d0c76ac60e7f5a171b9325a5f3ff 39.874120581000 730195 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": 358344, "vin": [ { "gen": { "height": 358334 } } ], "vout": [ { "amount": 39874120581, "target": { "key": "e392df9a8badf9d3a4a06ad57c616923a547d0c76ac60e7f5a171b9325a5f3ff" } } ], "extra": [ 1, 5, 244, 234, 157, 215, 71, 196, 6, 229, 50, 250, 86, 170, 207, 123, 169, 83, 218, 41, 39, 3, 239, 101, 137, 234, 141, 198, 170, 59, 60, 226, 161, 2, 17, 0, 0, 0, 4, 148, 254, 73, 66, 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