← previous blocknext block →recent activity
Analyzing
Block #96,132,003
27 transactions · 19 stateful · 2026-08-15 06:28:43 UTC
Parallelism
78/100
Blocked
53%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,132,003 · 27 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w410w111w012w115w020w222w323w425w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3f5b9011…1bae
0x34b655…2a6f
10 touches
10 conflicts
0x94e40668…1943
0xd32edf…ff58
9 touches
10 conflicts
0x9a3463f0…0b73
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x34d2db05…ba5c
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
10 conflicts on slot 0x3f5b90111b…d71bae
Audit this contract →
← previous block·next block →recent activity