← previous blocknext block →recent activity
Analyzing
Block #96,034,001
12 transactions · 9 stateful · 2026-08-14 22:15:47 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,034,001 · 12 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
9w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6864dd7…0df8
0x34b655…2a6f
4 touches
1 conflict
0x43076802…d920
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x117e581f…7b67
0x34b655…2a6f
2 touches
0 conflicts
0x11f6c101…9e2f
0x34b655…2a6f
2 touches
0 conflicts
0x18e86f02…fa98
0x34b655…2a6f
2 touches
0 conflicts
0x31b39922…1e66
0x34b655…2a6f
2 touches
0 conflicts
0x3f25409b…f92b
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 0xb6864dd73b…b40df8
Audit this contract →
← previous block·next block →recent activity