← previous blocknext block →recent activity
Analyzing
Block #94,663,463
7 transactions · 6 stateful · 2026-08-10 03:04:45 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,663,463 · 7 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf3383813…4a0c
0x34b655…2a6f
4 touches
1 conflict
0xf561e9b8…b6a1
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x5a810441…bf4a
0x34b655…2a6f
4 touches
1 conflict
0x23b06bf5…1693
0x34b655…2a6f
2 touches
0 conflicts
0x23b06bf5…1694
0x34b655…2a6f
2 touches
0 conflicts
0x51087f5a…61f7
0x34b655…2a6f
2 touches
0 conflicts
0x5473b646…7574
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
1 conflict on slot 0xf338381336…ec4a0c
Audit this contract →
← previous block·next block →recent activity