← previous blocknext block →recent activity
Analyzing
Block #96,354,856
13 transactions · 13 stateful · 2026-08-16 01:09:36 UTC
Parallelism
85/100
Blocked
23%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,354,856 · 13 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
3w06w08w110w011w112w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x91e8d927…3a11
0x34b655…2a6f
4 touches
1 conflict
0xc3fc40da…1c60
0x34b655…2a6f
4 touches
1 conflict
0x7e32f1e0…5612
0x77d53b…8080
4 touches
1 conflict
0xe3abe489…ebf2
0x77d53b…8080
4 touches
1 conflict
0xf101bd5c…0d6c
0x77d53b…8080
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x7938c6fd…1cd1
0x34b655…2a6f
4 touches
1 conflict
0xd5fbd3e3…49bc
0x69d57b…cc2f
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 0x91e8d92738…953a11
Audit this contract →
← previous block·next block →recent activity