← previous blocknext block →recent activity
Analyzing
Block #96,209,217
15 transactions · 12 stateful · 2026-08-15 12:57:05 UTC
Parallelism
80/100
Blocked
42%
Avg conflicts / tx
0.47
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,209,217 · 15 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
2w03w14w27w08w113w114w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbffde283…3385
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x35a9f06c…7689
0x34b655…2a6f
4 touches
1 conflict
0x32164862…19d1
0x34b655…2a6f
2 touches
0 conflicts
0x67a075d3…bb1d
0x34b655…2a6f
2 touches
0 conflicts
0x77ea8cfe…b5c7
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 0xbffde283d8…c63385
Audit this contract →
← previous block·next block →recent activity