← previous blocknext block →recent activity
Analyzing
Block #96,491,228
5 transactions · 3 stateful · 2026-08-16 12:35:29 UTC
Parallelism
60/100
Blocked
33%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,491,228 · 5 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c8898de…8758
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x044844a0…7418
0x34b655…2a6f
2 touches
0 conflicts
0x143c16d2…5e4d
0x34b655…2a6f
2 touches
0 conflicts
0x21f2dd42…3430
0x34b655…2a6f
2 touches
0 conflicts
0x68a6a4e5…e631
0x34b655…2a6f
2 touches
0 conflicts
0x6a0e4887…6fde
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 0x6c8898de19…1f8758
Audit this contract →
← previous block·next block →recent activity