← previous blocknext block →recent activity
Analyzing
Block #94,209,097
10 transactions · 8 stateful · 2026-08-08 12:47:06 UTC
Parallelism
70/100
Blocked
38%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,209,097 · 10 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w15w26w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc91d4275…1d7c
0x34b655…2a6f
4 touches
1 conflict
0xd29f7fca…f6f1
0x065c9d…c394
4 touches
1 conflict
0xe30c1f62…49ae
0x34b655…2a6f
4 touches
1 conflict
0x4c1fbdf6…953d
0x754704…b603
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xf7adce63…0fd2
0x754704…b603
4 touches
1 conflict
0x0ddfdaf2…9e00
0x34b655…2a6f
4 touches
1 conflict
0x5502e1cc…3910
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
1 conflict on slot 0xc91d427585…fe1d7c
Audit this contract →
← previous block·next block →recent activity