← previous blocknext block →recent activity
Analyzing
Block #95,008,918
16 transactions · 15 stateful · 2026-08-11 08:03:50 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,008,918 · 16 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
6w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb7b1a9a4…0c7e
0x34b655…2a6f
4 touches
1 conflict
0xb7b1a9a4…0c7f
0x34b655…2a6f
4 touches
1 conflict
0x291ad0b4…69e9
0x34b655…2a6f
4 touches
1 conflict
0xc7548347…e951
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x5a6864fe…2890
0x34b655…2a6f
2 touches
0 conflicts
0x6bf71f68…fd07
0x34b655…2a6f
2 touches
0 conflicts
0x71806e15…2893
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 0xb7b1a9a422…810c7e
Audit this contract →
← previous block·next block →recent activity