← previous blocknext block →recent activity
Analyzing
Block #94,744,160
22 transactions · 20 stateful · 2026-08-10 09:51:27 UTC
Parallelism
64/100
Blocked
50%
Avg conflicts / tx
1.55
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #94,744,160 · 22 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
1w02w13w04w05w16w27w310w411w515w517w620w621w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x93b6fab0…09d6
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x22c2bb0c…9d5d
0x34b655…2a6f
4 touches
1 conflict
0x22c44de4…44de
0x34b655…2a6f
4 touches
1 conflict
0x2afe51f4…4006
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x762e0aff…d3fd
0x34b655…2a6f
4 touches
1 conflict
0xef9cfcf5…1bc0
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
28 conflicts on slot 0x93b6fab01a…2d09d6
Audit this contract →
← previous block·next block →recent activity