← previous blocknext block →recent activity
Analyzing
Block #96,709,445
13 transactions · 13 stateful · 2026-08-17 06:53:19 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,709,445 · 13 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
2w03w04w15w16w28w09w310w211w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1ffa9f70…0e39
0x34b655…2a6f
6 touches
3 conflicts
0xefeb7937…c283
0x34b655…2a6f
6 touches
3 conflicts
0xb3fb9fb5…64db
0x34b655…2a6f
6 touches
3 conflicts
0x4cabb80a…46bf
0x34b655…2a6f
6 touches
3 conflicts
0x4c3f4858…52de
0x34b655…2a6f
6 touches
3 conflicts
0xf1e2f456…7422
0x34b655…2a6f
4 touches
1 conflict
0x52b477bc…7ccf
0x34b655…2a6f
4 touches
1 conflict
0x734ee320…caae
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 0x1ffa9f7040…490e39
Audit this contract →
← previous block·next block →recent activity