← previous blocknext block →recent activity
Analyzing
Block #96,373,832
14 transactions · 13 stateful · 2026-08-16 02:45:03 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,373,832 · 14 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
2w03w15w08w29w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafb8e71e…9285
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xe021dbc8…d27b
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xb11d2a1d…239f
0x34b655…2a6f
4 touches
1 conflict
0x177d036a…1c5d
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 0xafb8e71eb0…ec9285
Audit this contract →
← previous block·next block →recent activity