← previous blocknext block →recent activity
Analyzing
Block #94,199,393
15 transactions · 13 stateful · 2026-08-08 11:58:01 UTC
Parallelism
60/100
Blocked
62%
Avg conflicts / tx
1.27
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,199,393 · 15 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w47w58w09w110w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4cabb80a…46bf
0x34b655…2a6f
12 touches
15 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x1c5aed73…e93c
0x34b655…2a6f
4 touches
1 conflict
0x5d4a544d…41f3
0x34b655…2a6f
4 touches
1 conflict
0x64a785e4…0110
0x34b655…2a6f
4 touches
1 conflict
0x6bf4acb7…93da
0x34b655…2a6f
4 touches
1 conflict
0x0adf48a7…c84a
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
15 conflicts on slot 0x4cabb80a0e…7546bf
Audit this contract →
← previous block·next block →recent activity