← previous blocknext block →recent activity
Analyzing
Block #96,436,289
11 transactions · 7 stateful · 2026-08-16 07:59:08 UTC
Parallelism
73/100
Blocked
29%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,436,289 · 11 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
7w08w19w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfe449cf3…289f
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b78
0x34b655…2a6f
4 touches
1 conflict
0x9e6be63e…d886
0x34b655…2a6f
4 touches
1 conflict
0xa367eff3…1905
0x2880ab…7b43
2 touches
0 conflicts
0xa367eff3…1906
0x2880ab…7b43
2 touches
0 conflicts
0x085df2c1…305a
0x34b655…2a6f
2 touches
0 conflicts
0x147a1e75…aefb
0x34b655…2a6f
2 touches
0 conflicts
0x167de262…f61f
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 0xfe449cf3cc…14289f
Audit this contract →
← previous block·next block →recent activity