← previous blocknext block →recent activity
Analyzing
Block #94,484,187
29 transactions · 26 stateful · 2026-08-09 12:03:04 UTC
Parallelism
59/100
Blocked
65%
Avg conflicts / tx
2
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #94,484,187 · 29 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w05w16w27w38w39w410w511w612w720w121w825w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x95c47f03…f1bb
0x34b655…2a6f
14 touches
21 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
10 touches
10 conflicts
0xcc351d6d…256b
0x34b655…2a6f
10 touches
10 conflicts
0xec7d120d…7084
0x34b655…2a6f
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x8635a342…4e8b
0x34b655…2a6f
6 touches
3 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
21 conflicts on slot 0x95c47f0322…51f1bb
Audit this contract →
← previous block·next block →recent activity