← previous blocknext block →recent activity
Analyzing
Block #94,719,172
12 transactions · 12 stateful · 2026-08-10 07:44:57 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,719,172 · 12 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
1w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd064a456…b881
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xcf840bd3…7a02
0x34b655…2a6f
4 touches
1 conflict
0x0610892c…fee0
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x3601aa45…29cb
0x34b655…2a6f
2 touches
0 conflicts
0x3f25409b…f92b
0x34b655…2a6f
2 touches
0 conflicts
0x4327afd2…1b3a
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 0xd064a456fe…30b881
Audit this contract →
← previous block·next block →recent activity