← previous blocknext block →recent activity
Analyzing
Block #94,686,052
22 transactions · 21 stateful · 2026-08-10 04:58:23 UTC
Parallelism
91/100
Blocked
19%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #94,686,052 · 22 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
1w02w04w07w18w112w115w021w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa07e7b13…7513
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xb5dab803…6922
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x5dbb73e8…739f
0x34b655…2a6f
4 touches
1 conflict
0x06e6ff87…e712
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: Perpl
1 conflict on slot 0xa07e7b13f3…e77513
Audit this contract →
← previous block·next block →recent activity