← previous blocknext block →recent activity
Analyzing
Block #96,424,306
15 transactions · 13 stateful · 2026-08-16 06:58:53 UTC
Parallelism
87/100
Blocked
8%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,424,306 · 15 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
2w03w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5d2e788d…5867
0x34b655…2a6f
4 touches
1 conflict
0x632a3f89…c958
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x0feb12c1…5cc6
0x34b655…2a6f
2 touches
0 conflicts
0x23a320fb…cbd7
0x34b655…2a6f
2 touches
0 conflicts
0x424934c8…f2f1
0x34b655…2a6f
2 touches
0 conflicts
0x4b13022d…dc04
0x34b655…2a6f
2 touches
0 conflicts
0x833f3561…bfd0
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 0x5d2e788d21…445867
Audit this contract →
← previous block·next block →recent activity