← previous blocknext block →recent activity
Analyzing
Block #96,214,282
11 transactions · 9 stateful · 2026-08-15 13:22:34 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.36
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,214,282 · 11 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
1w02w13w17w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x159cff26…7665
0x34b655…2a6f
4 touches
1 conflict
0x9a3463f0…0b73
0x34b655…2a6f
4 touches
1 conflict
0xa5a8ffca…8de2
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x32b804b3…ce18
0x34b655…2a6f
2 touches
0 conflicts
0x36672bdc…8e4a
0x34b655…2a6f
2 touches
0 conflicts
0x3ff64add…ea90
0x34b655…2a6f
2 touches
0 conflicts
0x42df06bf…3fac
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 0x159cff262c…e57665
Audit this contract →
← previous block·next block →recent activity