← previous blocknext block →recent activity
Analyzing
Block #96,603,452
15 transactions · 13 stateful · 2026-08-16 22:00:14 UTC
Parallelism
73/100
Blocked
23%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,603,452 · 15 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
1w03w04w16w210w014w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x4acbdbcf…a8c6
0x34b655…2a6f
8 touches
6 conflicts
0xae4e59c4…7029
0x34b655…2a6f
6 touches
3 conflicts
0x54998534…d4dd
0x34b655…2a6f
6 touches
3 conflicts
0xc4998e49…c79d
0x34b655…2a6f
4 touches
1 conflict
0xe0f449fb…30e9
0x34b655…2a6f
4 touches
1 conflict
0xec7d120d…7084
0x34b655…2a6f
4 touches
1 conflict
0x840d3ab7…c8c4
0x34b655…2a6f
4 touches
1 conflict
0xb9834665…e363
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
6 conflicts on slot 0x4acbdbcf7f…d0a8c6
Audit this contract →
← previous block·next block →recent activity