← previous blocknext block →recent activity
Analyzing
Block #96,567,064
16 transactions · 15 stateful · 2026-08-16 18:57:12 UTC
Parallelism
88/100
Blocked
7%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,567,064 · 16 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
4w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe39a1f7…8eb0
0x34b655…2a6f
4 touches
1 conflict
0xeeb46b9e…93e1
0x34b655…2a6f
4 touches
1 conflict
0x07bb3f5a…617e
0x34b655…2a6f
2 touches
0 conflicts
0x14eb2f47…8a2e
0x34b655…2a6f
2 touches
0 conflicts
0x34a1ee7e…fb20
0x34b655…2a6f
2 touches
0 conflicts
0x6be61178…1cb3
0x34b655…2a6f
2 touches
0 conflicts
0x7fa44fe8…484e
0x34b655…2a6f
2 touches
0 conflicts
0xbde524f4…43bf
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 0xfe39a1f75c…758eb0
Audit this contract →
← previous block·next block →recent activity