← previous blocknext block →recent activity
Analyzing
Block #98,380,322
20 transactions · 18 stateful · 2026-08-23 04:12:26 UTC
Parallelism
80/100
Blocked
17%
Avg conflicts / tx
0.2
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,380,322 · 20 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
3w04w112w218w019w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x9ef9caab…9c45
0x34b655…2a6f
4 touches
1 conflict
0xc719def3…ebeb
0x34b655…2a6f
4 touches
1 conflict
0x34d2db05…ba5c
0x34b655…2a6f
3 touches
1 conflict
0xba5743c7…21c1
0x1b6862…e19c
2 touches
0 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: Perpl
1 conflict on slot 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity