← previous blocknext block →recent activity
Analyzing
Block #96,143,712
12 transactions · 10 stateful · 2026-08-15 07:27:38 UTC
Parallelism
75/100
Blocked
50%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,143,712 · 12 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
1w02w03w14w05w16w18w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe73b93bf…c0e1
0x34b655…2a6f
6 touches
3 conflicts
0xa6464996…3af9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xf481d314…3fdd
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x915c095e…c1e5
0x2b46c0…1669
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
3 conflicts on slot 0xe73b93bf37…0bc0e1
Audit this contract →
← previous block·next block →recent activity