← previous blocknext block →recent activity
Analyzing
Block #95,243,532
7 transactions · 6 stateful · 2026-08-12 03:44:46 UTC
Parallelism
57/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #95,243,532 · 7 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x32b804b3…ce18
0x34b655…2a6f
4 touches
1 conflict
0x61d1a6fa…86fe
0x34b655…2a6f
4 touches
1 conflict
0x01dada3b…0aa7
0x34b655…2a6f
2 touches
0 conflicts
0x01dada3b…0aa8
0x34b655…2a6f
2 touches
0 conflicts
0x04ccc0f7…a945
0x34b655…2a6f
2 touches
0 conflicts
0x0600e909…c4f2
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
3 conflicts on slot 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity