← previous blocknext block →recent activity
Analyzing
Block #96,291,184
16 transactions · 15 stateful · 2026-08-15 19:49:22 UTC
Parallelism
75/100
Blocked
47%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,291,184 · 16 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
1w02w13w24w05w111w113w214w315w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ad82ccb…b08b
0x34b655…2a6f
6 touches
3 conflicts
0x932a9590…0b19
0x34b655…2a6f
6 touches
3 conflicts
0x59be4750…deac
0x34b655…2a6f
5 touches
3 conflicts
0xbb97db90…4c93
0xc8689a…ee79
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xc4998e49…c79d
0x34b655…2a6f
4 touches
1 conflict
0xc5a78c51…2753
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…641f
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
3 conflicts on slot 0x9ad82ccb7a…3bb08b
Audit this contract →
← previous block·next block →recent activity