← previous blocknext block →recent activity
Analyzing
Block #94,171,005
15 transactions · 13 stateful · 2026-08-08 09:34:00 UTC
Parallelism
73/100
Blocked
31%
Avg conflicts / tx
0.33
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #94,171,005 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w28w010w311w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90d93553…b73a
0x34b655…2a6f
6 touches
3 conflicts
0x42c27cea…b5f3
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd077a617…2f11
0x34b655…2a6f
4 touches
1 conflict
0xe2e52e46…0894
0x34b655…2a6f
4 touches
1 conflict
0x875dd001…c5d9
0x40c49f…2af0
4 touches
1 conflict
0x38855b14…b4ec
0x34b655…2a6f
2 touches
0 conflicts
0x3cf50d44…961b
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
3 conflicts on slot 0x90d935536d…5bb73a
Audit this contract →
← previous block·next block →recent activity