← previous blocknext block →recent activity
Analyzing
Block #98,087,645
23 transactions · 19 stateful · 2026-08-22 03:39:14 UTC
Parallelism
83/100
Blocked
42%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,087,645 · 23 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
1w02w04w05w16w07w110w011w114w015w216w117w121w322w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x152a2f3e…13f8
0x34b655…2a6f
6 touches
3 conflicts
0x31aff8d8…1e66
0x34b655…2a6f
4 touches
1 conflict
0x31c88cf2…107f
0x34b655…2a6f
4 touches
1 conflict
0x3fff7ccd…5a48
0x34b655…2a6f
4 touches
1 conflict
0x4a5956ef…e226
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x5e0b8bbe…377b
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
6 conflicts on slot 0xe5bb3628b5…71e5f1
Audit this contract →
← previous block·next block →recent activity