← previous blocknext block →recent activity
Analyzing
Block #94,790,556
10 transactions · 9 stateful · 2026-08-10 13:45:29 UTC
Parallelism
70/100
Blocked
22%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,790,556 · 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
1w02w03w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfbe6a366…8ca1
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x03aa8b26…118a
0x34b655…2a6f
2 touches
0 conflicts
0x08ae6453…ebfa
0x34b655…2a6f
2 touches
0 conflicts
0x2741e3b9…944b
0x34b655…2a6f
2 touches
0 conflicts
0x30c0f89e…b0db
0x34b655…2a6f
2 touches
0 conflicts
0x48a57d5f…bdd0
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 0xfbe6a36638…508ca1
Audit this contract →
← previous block·next block →recent activity