← previous blocknext block →recent activity
Analyzing
Block #96,087,602
8 transactions · 6 stateful · 2026-08-15 02:45:22 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,087,602 · 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
1w02w03w04w15w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe4af4c87…9964
0x34b655…2a6f
4 touches
1 conflict
0x6a4868a5…367e
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4cabb80a…46bf
0x34b655…2a6f
4 touches
1 conflict
0x177d036a…1c5d
0x34b655…2a6f
2 touches
0 conflicts
0x2021fb2a…d63b
0x34b655…2a6f
2 touches
0 conflicts
0x53f393fa…00b9
0x34b655…2a6f
2 touches
0 conflicts
0x57f53b5f…e511
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 0xe4af4c87c3…c59964
Audit this contract →
← previous block·next block →recent activity