← previous blocknext block →recent activity
Analyzing
Block #99,180,923
24 transactions · 24 stateful · 2026-08-26 00:03:35 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,180,923 · 24 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
2w03w14w05w17w08w19w012w014w015w118w120w223w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd957b700…32be
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xf5b5f7…6d70
4 touches
1 conflict
0xfe65bb7b…12d7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
4 touches
1 conflict
0x065ff70b…356d
0x40c49f…2af0
4 touches
1 conflict
0x5cf3c3d7…fe0a
0x40c49f…2af0
4 touches
1 conflict
0xaa279ab9…bf08
0x40c49f…2af0
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
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 0xd957b70053…1a32be
Audit this contract →
← previous block·next block →recent activity