← previous blocknext block →recent activity
Analyzing
Block #95,194,479
8 transactions · 6 stateful · 2026-08-11 23:38:02 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,194,479 · 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6799eba…78e7
0x34b655…2a6f
4 touches
1 conflict
0x0a57a2b8…3cdd
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
0x34b655…2a6f
4 touches
1 conflict
0x1ca9a6de…019e
0x34b655…2a6f
2 touches
0 conflicts
0x5546a1e2…e8df
0x34b655…2a6f
2 touches
0 conflicts
0x58e0697b…aaa5
0x34b655…2a6f
2 touches
0 conflicts
0x6da38b56…1d55
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 0xf6799ebad0…1778e7
Audit this contract →
← previous block·next block →recent activity