← previous blocknext block →recent activity
Analyzing
Block #99,263,859
21 transactions · 21 stateful · 2026-08-26 07:00:58 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.52
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,263,859 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w07w08w110w111w212w014w116w219w020w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8493e8c8…5ff4
0x34b655…2a6f
6 touches
3 conflicts
0x4c29ecd5…58b6
0x34b655…2a6f
6 touches
3 conflicts
0xad601853…1d2a
0x34b655…2a6f
6 touches
3 conflicts
0xe1c4e5ce…0dec
0x34b655…2a6f
6 touches
3 conflicts
0xfe45073e…6315
0x34b655…2a6f
6 touches
3 conflicts
0x7006165a…df17
0x34b655…2a6f
4 touches
1 conflict
0x7a3d5e6f…7864
0x34b655…2a6f
4 touches
1 conflict
0x7aa463de…e7b8
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 0x8493e8c8df…0f5ff4
Audit this contract →
← previous block·next block →recent activity