← previous blocknext block →recent activity
Analyzing
Block #96,047,623
21 transactions · 20 stateful · 2026-08-14 23:24:19 UTC
Parallelism
62/100
Blocked
40%
Avg conflicts / tx
1.57
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,047,623 · 21 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w05w16w17w28w311w413w514w618w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x427c9fc4…5cee
0x34b655…2a6f
16 touches
28 conflicts
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x19439a65…eb51
0x34b655…2a6f
6 touches
3 conflicts
0x96d1711a…347c
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x7b55198a…b946
0x34b655…2a6f
6 touches
3 conflicts
0xa33e4ca4…e6c7
0x34b655…2a6f
4 touches
1 conflict
0xb3fb9fb5…64db
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
28 conflicts on slot 0x427c9fc46b…895cee
Audit this contract →
← previous block·next block →recent activity