Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 52f067d8315eac434564b5dea4a82f7d67941e4d54f016d90941c4498ebcc6cd

Tx prefix hash: ff9231f9558b73bb40e24bcf40a9a11483d5cd9ad9a2f3e0eb90524a2c1af875
Tx public key: 6e69f8764aa74a6d18ec7e74b3f2e84544c991a4129f6138b50620f36e24de34
Timestamp: 1596333971 Timestamp [UCT]: 2020-08-02 02:06:11 Age [y:d:h:m:s]: 05:068:17:13:56
Block: 122360 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.1006 kB
Tx version: 2 No of confirmations: 1263291 RingCT/type: yes/0
Extra: 016e69f8764aa74a6d18ec7e74b3f2e84544c991a4129f6138b50620f36e24de340211000000038a2ee0d9000000000000000000

1 output(s) for total of 241.317402031000 dcy

stealth address amount amount idx
00: 5a9e2d7039e7e2b4a30f4c918f26c4ec5c7e6d11819f8ab2819c301131243543 241.317402031000 207736 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": 122370, "vin": [ { "gen": { "height": 122360 } } ], "vout": [ { "amount": 241317402031, "target": { "key": "5a9e2d7039e7e2b4a30f4c918f26c4ec5c7e6d11819f8ab2819c301131243543" } } ], "extra": [ 1, 110, 105, 248, 118, 74, 167, 74, 109, 24, 236, 126, 116, 179, 242, 232, 69, 68, 201, 145, 164, 18, 159, 97, 56, 181, 6, 32, 243, 110, 36, 222, 52, 2, 17, 0, 0, 0, 3, 138, 46, 224, 217, 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