← previous blocknext block →recent activity
Analyzing
Block #98,743,866
22 transactions · 19 stateful · 2026-08-24 11:17:40 UTC
Parallelism
82/100
Blocked
58%
Avg conflicts / tx
0.73
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,743,866 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w25w16w17w28w29w313w316w017w318w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4f3a6b4a…3819
0x34b655…2a6f
6 touches
3 conflicts
0x17606ba6…1b6e
0x754704…b603
6 touches
3 conflicts
0x889d5e90…929a
0x2a68ba…90c5
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x33018431…8f5c
0x188d58…ea8e
4 touches
1 conflict
0x33018431…8f5d
0x188d58…ea8e
4 touches
1 conflict
0x469dac8d…3411
0x34b655…2a6f
4 touches
1 conflict
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: Perpl
3 conflicts on slot 0x4f3a6b4a49…e93819
Audit this contract →
← previous block·next block →recent activity