← previous blocknext block →recent activity
Analyzing
Block #96,131,819
20 transactions · 15 stateful · 2026-08-15 06:27:47 UTC
Parallelism
65/100
Blocked
47%
Avg conflicts / tx
0.9
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,131,819 · 20 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
2w03w14w25w314w415w516w617w018w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x35725c97…85b4
0x34b655…2a6f
10 touches
10 conflicts
0x1a2055c7…9054
0x34b655…2a6f
8 touches
6 conflicts
0x34cdb3c2…96d2
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0xd66696e0…0842
0x34b655…2a6f
8 touches
6 conflicts
0xe41b9671…e777
0x34b655…2a6f
8 touches
6 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
10 conflicts on slot 0x35725c9762…2785b4
Audit this contract →
← previous block·next block →recent activity