← previous blocknext block →recent activity
Analyzing
Block #98,427,824
24 transactions · 20 stateful · 2026-08-23 08:11:26 UTC
Parallelism
83/100
Blocked
30%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #98,427,824 · 24 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
3w010w111w212w314w015w016w119w122w023w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe5bb3628…e5f1
0x34b655…2a6f
8 touches
6 conflicts
0x21e8ab54…3b4b
0x34b655…2a6f
6 touches
3 conflicts
0xa56ae218…1fc5
0x34b655…2a6f
6 touches
3 conflicts
0x2d94ecd9…43db
0x34b655…2a6f
4 touches
1 conflict
0x3b5fbc7d…c8fe
0x34b655…2a6f
4 touches
1 conflict
0x438f4336…47c9
0x34b655…2a6f
4 touches
1 conflict
0x55548428…0ab9
0x34b655…2a6f
4 touches
1 conflict
0x589605bf…7f62
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