← previous blocknext block →recent activity
Analyzing
Block #94,989,607
10 transactions · 9 stateful · 2026-08-11 06:26:41 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,989,607 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x38bdc5d3…a632
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
4 touches
1 conflict
0x93ffcd76…894e
0x34b655…2a6f
4 touches
1 conflict
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0x403abfb4…7399
0x851145…3f07
3 touches
1 conflict
0x0d9cfd39…39a7
0x34b655…2a6f
2 touches
0 conflicts
0x9ef38617…f0f2
0x34b655…2a6f
2 touches
0 conflicts
0xb2d5d74d…5e95
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 0x38bdc5d3e1…01a632
Audit this contract →
← previous block·next block →recent activity