← previous blocknext block →recent activity
Analyzing
Block #99,369,531
8 transactions · 8 stateful · 2026-08-26 15:52:48 UTC
Parallelism
63/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #99,369,531 · 8 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
2w04w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xdc8d7edd…8a03
0x34b655…2a6f
4 touches
1 conflict
0x62910921…3016
0x34b655…2a6f
4 touches
1 conflict
0x7cfb984a…4d58
0x34b655…2a6f
4 touches
1 conflict
0x0a6eee09…6393
0x34b655…2a6f
2 touches
0 conflicts
0x10af567c…3266
0x34b655…2a6f
2 touches
0 conflicts
0x20790169…cfbd
0x34b655…2a6f
2 touches
0 conflicts
0x2155a59c…17e0
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity