← previous blocknext block →recent activity
Analyzing
Block #94,980,969
10 transactions · 10 stateful · 2026-08-11 05:43:15 UTC
Parallelism
80/100
Blocked
20%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,980,969 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x07b86c51…cdae
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x8ebef559…b67c
0x851145…3f07
3 touches
1 conflict
0x0acc676f…a9bf
0x34b655…2a6f
2 touches
0 conflicts
0x13306c72…fb14
0x34b655…2a6f
2 touches
0 conflicts
0x1a9f678f…302a
0x34b655…2a6f
2 touches
0 conflicts
0x2b0eb207…93b5
0x34b655…2a6f
2 touches
0 conflicts
0x2fdfa032…139c
0x34b655…2a6f
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: Kuru Exchange: MarginAccount
1 conflict on slot 0x07b86c515d…73cdae
Audit this contract →
← previous block·next block →recent activity