← previous blocknext block →recent activity
Analyzing
Block #96,542,100
17 transactions · 16 stateful · 2026-08-16 16:51:39 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,542,100 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w27w18w210w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56a284d9…32e4
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0x886221b8…977e
0x34b655…2a6f
6 touches
3 conflicts
0xc39f2a27…f3a3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641d
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 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 0x56a284d9bf…3432e4
Audit this contract →
← previous block·next block →recent activity