← previous blocknext block →recent activity
Analyzing
Block #94,750,247
20 transactions · 20 stateful · 2026-08-10 10:22:24 UTC
Parallelism
60/100
Blocked
40%
Avg conflicts / tx
1.4
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,750,247 · 20 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w16w29w310w411w515w617w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x62a3f11b…03ec
0x34b655…2a6f
10 touches
10 conflicts
0xf3383813…4a0c
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x2db666e7…b931
0x34b655…2a6f
8 touches
6 conflicts
0x8ff85b19…dde0
0x34b655…2a6f
6 touches
3 conflicts
0xd66696e0…0842
0x34b655…2a6f
6 touches
3 conflicts
0x65f069f9…b5ff
0x34b655…2a6f
6 touches
3 conflicts
0xa3f095f5…bd87
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
10 conflicts on slot 0x62a3f11b78…4b03ec
Audit this contract →
← previous block·next block →recent activity