← previous blocknext block →recent activity
Analyzing
Block #95,648,294
8 transactions · 8 stateful · 2026-08-13 13:54:14 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,648,294 · 8 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6561b826…f343
0x34b655…2a6f
4 touches
1 conflict
0x198f3a22…7aeb
0x34b655…2a6f
4 touches
1 conflict
0x48203298…65cb
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
2 touches
0 conflicts
0x26607bc2…7fd6
0x34b655…2a6f
2 touches
0 conflicts
0x2d9c72fd…04a1
0x34b655…2a6f
2 touches
0 conflicts
0x46151ed3…d762
0x34b655…2a6f
2 touches
0 conflicts
0x53ca1284…cb2c
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 0x6561b82600…8ff343
Audit this contract →
← previous block·next block →recent activity