Dinastycoin Blockchain Explorer

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

Autorefresh is OFF

Tx hash: 422c5cb0f8ebf93c652b481ce3683dea424ebc2abe699ddad3628c4c291b487f

Tx prefix hash: 0ec8dbfed355a6dabbeea4bc2c5f2d3c9858359b60e87e84cb1129237cc88fa3
Tx public key: 8f50d1324a759eaf6d0edea0e2162433aacaf8e336b586f030b73056f95524ac
Timestamp: 1722007026 Timestamp [UCT]: 2024-07-26 15:17:06 Age [y:d:h:m:s]: 00:306:12:59:33
Block: 1074196 Fee (per_kB): 0.000000000000 (0.000000000000) Tx size: 0.0996 kB
Tx version: 2 No of confirmations: 219038 RingCT/type: yes/0
Extra: 018f50d1324a759eaf6d0edea0e2162433aacaf8e336b586f030b73056f95524ac02110000000ce914dd15000000000000000000

1 output(s) for total of 0.600000000000 dcy

stealth address amount amount idx
00: 9637b691cf7ff2ac17f970b0bac9c602ea817b1999821ac6aebe716b90e0fdfc 0.600000000000 1546709 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": 1074206, "vin": [ { "gen": { "height": 1074196 } } ], "vout": [ { "amount": 600000000, "target": { "key": "9637b691cf7ff2ac17f970b0bac9c602ea817b1999821ac6aebe716b90e0fdfc" } } ], "extra": [ 1, 143, 80, 209, 50, 74, 117, 158, 175, 109, 14, 222, 160, 226, 22, 36, 51, 170, 202, 248, 227, 54, 181, 134, 240, 48, 183, 48, 86, 249, 85, 36, 172, 2, 17, 0, 0, 0, 12, 233, 20, 221, 21, 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