← previous blocknext block →recent activity
Analyzing
Block #96,120,634
15 transactions · 15 stateful · 2026-08-15 05:31:30 UTC
Parallelism
53/100
Blocked
47%
Avg conflicts / tx
1.47
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,120,634 · 15 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w16w27w08w39w410w411w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
12 touches
15 conflicts
0x67a56c8b…f955
0x34b655…2a6f
10 touches
10 conflicts
0x50481519…304a
0x34b655…2a6f
10 touches
10 conflicts
0xc824469a…641f
0x34b655…2a6f
10 touches
10 conflicts
0xd09e14b2…d3ab
0x34b655…2a6f
9 touches
10 conflicts
0xe1c05076…acf1
0x34b655…2a6f
9 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0xeeb46b9e…93e1
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity