← previous blocknext block →recent activity
Analyzing
Block #94,485,773
13 transactions · 13 stateful · 2026-08-09 12:11:03 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,485,773 · 13 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
1w012w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x096c7f83…68af
0x34b655…2a6f
4 touches
1 conflict
0xb4e0a934…5fc7
0x34b655…2a6f
4 touches
1 conflict
0x0b000000…0002
0x000000…1000
2 touches
0 conflicts
0x0bbe8ee6…4ede
0x34b655…2a6f
2 touches
0 conflicts
0x15ae3bf3…2507
0x34b655…2a6f
2 touches
0 conflicts
0x25e6f91a…a6a4
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x3942bfcd…e059
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 0x096c7f8372…5e68af
Audit this contract →
← previous block·next block →recent activity