← previous blocknext block →recent activity
Analyzing
Block #94,842,308
18 transactions · 17 stateful · 2026-08-10 18:05:50 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #94,842,308 · 18 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
4w09w010w112w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd66a2f66…6e73
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7213
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…7215
0x34b655…2a6f
4 touches
1 conflict
0x7de57974…f5ba
0x34b655…2a6f
4 touches
1 conflict
0xf79df061…e005
0xe52b14…7230
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x62cc9214…441b
0x34b655…2a6f
2 touches
0 conflicts
0x943b92d0…dfee
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 0xd66a2f669c…306e73
Audit this contract →
← previous block·next block →recent activity