← previous blocknext block →recent activity
Analyzing
Block #95,278,222
12 transactions · 11 stateful · 2026-08-12 06:48:08 UTC
Parallelism
83/100
Blocked
18%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,278,222 · 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
1w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbe9baf16…df37
0x34b655…2a6f
4 touches
1 conflict
0x0672e4a2…8d1f
0x34b655…2a6f
4 touches
1 conflict
0x4a90f6e1…695a
0x34b655…2a6f
4 touches
1 conflict
0x00000000…009a
0x16f70c…c3dd
2 touches
0 conflicts
0x72a152dd…9d41
0x16f70c…c3dd
2 touches
0 conflicts
0x0a6f5e37…6c3c
0x34b655…2a6f
2 touches
0 conflicts
0x17cf10eb…0ec0
0x34b655…2a6f
2 touches
0 conflicts
0x2029b74e…c206
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 0xbe9baf16a9…e6df37
Audit this contract →
← previous block·next block →recent activity