Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 7688c9c90228fa801b8df1a5912f3ea82b34018f98b387085887753ba4ce894a

Tx prefix hash: 4a5c1dd936c97269b673a39158e439419377d545b69217926fb306e61a499e33
Tx public key: 126528e3ff67e1e385879a274d08ed9df0d9132743c1a99bb41c278e3b6c44c7
Timestamp: 1734676289 Timestamp [UCT]: 2024-12-20 06:31:29 Age [y:d:h:m:s]: 00:104:12:22:58
Block: 1179143 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 74448 RingCT/type: yes/0
Extra: 01126528e3ff67e1e385879a274d08ed9df0d9132743c1a99bb41c278e3b6c44c7021100000005007f978a000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: de15c53c54035051e2782035013bcf6e9108ca8e11f12e1f87fd90e8aab16098 0.600000000000 1665534 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": 1179153, "vin": [ { "gen": { "height": 1179143 } } ], "vout": [ { "amount": 600000000, "target": { "key": "de15c53c54035051e2782035013bcf6e9108ca8e11f12e1f87fd90e8aab16098" } } ], "extra": [ 1, 18, 101, 40, 227, 255, 103, 225, 227, 133, 135, 154, 39, 77, 8, 237, 157, 240, 217, 19, 39, 67, 193, 169, 155, 180, 28, 39, 142, 59, 108, 68, 199, 2, 17, 0, 0, 0, 5, 0, 127, 151, 138, 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