← previous blocknext block →recent activity
Analyzing
Block #96,156,016
8 transactions · 6 stateful · 2026-08-15 08:29:31 UTC
Parallelism
75/100
Blocked
17%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,156,016 · 8 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfcfc2ae3…972b
0x34b655…2a6f
4 touches
1 conflict
0x09396f14…669f
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
2 touches
0 conflicts
0x5655f5c3…6b75
0x34b655…2a6f
2 touches
0 conflicts
0x5e71af98…bfd6
0x34b655…2a6f
2 touches
0 conflicts
0x8ae3e2cf…d1a9
0x34b655…2a6f
2 touches
0 conflicts
0x9b68408a…e609
0x34b655…2a6f
2 touches
0 conflicts
0xcd93b2d2…30e6
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 0xfcfc2ae3f6…f3972b
Audit this contract →
← previous block·next block →recent activity