Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 6b0c911c7bcdc676eb47fa6a99dee2ee9bc5c2f9d826f1b54c8c295dab0cf8f5

Tx prefix hash: dd978f2cff043ddf4b9200d6185a1dae33d4c318c6db7906b94a7a1c0a6f66d1
Tx public key: ebb062baa64275b9d0351de21671cb9e3cb7fd7e4543ae1c5819fedd60ddbf2e
Timestamp: 1722941078 Timestamp [UCT]: 2024-08-06 10:44:38 Age [y:d:h:m:s]: 00:281:04:58:11
Block: 1081933 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 200913 RingCT/type: yes/0
Extra: 01ebb062baa64275b9d0351de21671cb9e3cb7fd7e4543ae1c5819fedd60ddbf2e02110000000491e13c04000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: b2e49c66452ce6dfb92870b1030cd0af468024560437c9c84ec31fc3b52ff7e0 0.600000000000 1555756 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": 1081943, "vin": [ { "gen": { "height": 1081933 } } ], "vout": [ { "amount": 600000000, "target": { "key": "b2e49c66452ce6dfb92870b1030cd0af468024560437c9c84ec31fc3b52ff7e0" } } ], "extra": [ 1, 235, 176, 98, 186, 166, 66, 117, 185, 208, 53, 29, 226, 22, 113, 203, 158, 60, 183, 253, 126, 69, 67, 174, 28, 88, 25, 254, 221, 96, 221, 191, 46, 2, 17, 0, 0, 0, 4, 145, 225, 60, 4, 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