← previous blocknext block →recent activity
Analyzing
Block #96,024,419
8 transactions · 8 stateful · 2026-08-14 21:27:34 UTC
Parallelism
50/100
Blocked
38%
Avg conflicts / tx
1
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,024,419 · 8 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w05w26w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x25ecf913…0ad8
0x34b655…2a6f
8 touches
6 conflicts
0xa8c5904c…e1a7
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x0fb9e50c…1a35
0x34b655…2a6f
4 touches
1 conflict
0xb8b82811…8b9e
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35d
0x34b655…2a6f
4 touches
1 conflict
0x261cbea7…e35e
0x34b655…2a6f
4 touches
1 conflict
0x31616f97…1acc
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
6 conflicts on slot 0x25ecf913e7…100ad8
Audit this contract →
← previous block·next block →recent activity