← previous blocknext block →recent activity
Analyzing
Block #98,434,295
11 transactions · 11 stateful · 2026-08-23 08:43:59 UTC
Parallelism
82/100
Blocked
18%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #98,434,295 · 11 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x886db264…846e
0x34b655…2a6f
4 touches
1 conflict
0x9a8af3c2…e4ae
0x34b655…2a6f
4 touches
1 conflict
0x00838cee…1504
0x34b655…2a6f
4 touches
1 conflict
0xd541a808…4002
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x522e20b4…fbc4
0x34b655…2a6f
3 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
1 conflict on slot 0x886db2649c…07846e
Audit this contract →
← previous block·next block →recent activity