← previous blocknext block →recent activity
Analyzing
Block #96,447,368
5 transactions · 4 stateful · 2026-08-16 08:54:51 UTC
Parallelism
40/100
Blocked
50%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,447,368 · 5 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
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x66bdb4c2…7ea6
0x34b655…2a6f
4 touches
1 conflict
0x0460135c…98fd
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x00e2c296…0001
0x34b655…2a6f
2 touches
0 conflicts
0x05286dbb…4517
0x34b655…2a6f
2 touches
0 conflicts
0x1bd6ddeb…9a19
0x34b655…2a6f
2 touches
0 conflicts
0x1f02c5ca…02d7
0x34b655…2a6f
2 touches
0 conflicts
0x312e9622…f814
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 0x66bdb4c268…a97ea6
Audit this contract →
← previous block·next block →recent activity