← previous blocknext block →recent activity
Analyzing
Block #96,828,903
12 transactions · 12 stateful · 2026-08-17 16:54:10 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.92
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,828,903 · 12 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w06w17w29w110w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb1b58b33…874f
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
4 touches
1 conflict
0x02d895f0…2b93
0x34b655…2a6f
4 touches
1 conflict
0x363a4317…87d2
0x34b655…2a6f
4 touches
1 conflict
0x3e6302c8…64f5
0x34b655…2a6f
4 touches
1 conflict
0x472e66d6…7003
0x34b655…2a6f
4 touches
1 conflict
0x4bc1b6fd…ce27
0x34b655…2a6f
4 touches
1 conflict
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 0xb1b58b3385…e4874f
Audit this contract →
← previous block·next block →recent activity