← previous blocknext block →recent activity
Analyzing
Block #98,756,789
25 transactions · 24 stateful · 2026-08-24 12:22:49 UTC
Parallelism
80/100
Blocked
46%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #98,756,789 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w19w211w013w014w115w217w118w219w320w223w324w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc84cdfcc…2332
0x8964d7…10f8
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x2a07e64e…fe77
0x754704…b603
8 touches
6 conflicts
0x00000000…0008
0x8964d7…10f8
8 touches
6 conflicts
0xc84cdfcc…232b
0x8964d7…10f8
8 touches
6 conflicts
0xc84cdfcc…232c
0x8964d7…10f8
8 touches
6 conflicts
0xc84cdfcc…232f
0x8964d7…10f8
8 touches
6 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: 0x8964d7c9…5b10f8
6 conflicts on slot 0xc84cdfcc46…872332
Audit this contract →
← previous block·next block →recent activity