← previous blocknext block →recent activity
Analyzing
Block #96,340,054
17 transactions · 15 stateful · 2026-08-15 23:55:09 UTC
Parallelism
65/100
Blocked
53%
Avg conflicts / tx
0.94
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,340,054 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w210w311w312w413w414w116w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x424934c8…f2f1
0x34b655…2a6f
8 touches
6 conflicts
0x4c188934…158e
0x34b655…2a6f
6 touches
3 conflicts
0xcdd32c46…e107
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xfb2c679b…4335
0x34b655…2a6f
6 touches
3 conflicts
0x81561f70…fefd
0x34b655…2a6f
4 touches
1 conflict
0x91e8d927…3a11
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
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 0x424934c865…4af2f1
Audit this contract →
← previous block·next block →recent activity