← previous blocknext block →recent activity
Analyzing
Block #95,717,837
22 transactions · 21 stateful · 2026-08-13 19:45:04 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.55
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #95,717,837 · 22 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w27w08w111w013w014w116w117w018w120w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08636046…e60f
0x34b655…2a6f
8 touches
6 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xeae24c…0be0
4 touches
1 conflict
0x7747c10a…3219
0x968279…9342
4 touches
1 conflict
0x7747c10a…321a
0x968279…9342
4 touches
1 conflict
0x7747c10a…321c
0x968279…9342
4 touches
1 conflict
0xc6b1d981…1be2
0xa6afd3…d132
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
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
6 conflicts on slot 0x08636046fc…69e60f
Audit this contract →
← previous block·next block →recent activity