← previous blocknext block →recent activity
Analyzing
Block #94,673,555
9 transactions · 8 stateful · 2026-08-10 03:55:30 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,673,555 · 9 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0xc8024a74…4685
0x34b655…2a6f
4 touches
1 conflict
0x75f108dc…f5a7
0x34b655…2a6f
3 touches
1 conflict
0x4f1ad4b4…e00a
0x34b655…2a6f
2 touches
0 conflicts
0x4f89e431…499f
0x34b655…2a6f
2 touches
0 conflicts
0x5502e1cc…3910
0x34b655…2a6f
2 touches
0 conflicts
0x56a653f2…7434
0x34b655…2a6f
2 touches
0 conflicts
0x6f6b4878…d72d
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 0xbde524f475…b143bf
Audit this contract →
← previous block·next block →recent activity