← previous blocknext block →recent activity
Analyzing
Block #96,388,793
7 transactions · 5 stateful · 2026-08-16 04:00:17 UTC
Parallelism
71/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,388,793 · 7 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
2w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x513b0c80…d2d9
0x34b655…2a6f
4 touches
1 conflict
0x74cf37b3…dd1a
0x34b655…2a6f
4 touches
1 conflict
0xefa62407…733d
0x34b655…2a6f
4 touches
1 conflict
0xf63c2a2b…bc5f
0x34b655…2a6f
4 touches
1 conflict
0xf63c2a2b…bc60
0x34b655…2a6f
4 touches
1 conflict
0x49d62ab0…e169
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
2 touches
0 conflicts
0x7e1d87b8…291c
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 0x513b0c80f3…fbd2d9
Audit this contract →
← previous block·next block →recent activity