← previous blocknext block →recent activity
Analyzing
Block #94,809,357
20 transactions · 19 stateful · 2026-08-10 15:20:04 UTC
Parallelism
65/100
Blocked
42%
Avg conflicts / tx
0.7
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,809,357 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w08w09w110w115w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x5a19ef35…dc70
0x34b655…2a6f
6 touches
3 conflicts
0x41240dde…04b9
0x34b655…2a6f
6 touches
3 conflicts
0x54526994…55b2
0x34b655…2a6f
6 touches
3 conflicts
0xacea03ce…0f23
0x34b655…2a6f
6 touches
3 conflicts
0x4783345c…4a90
0x34b655…2a6f
4 touches
1 conflict
0x5fe55f49…aa34
0x34b655…2a6f
4 touches
1 conflict
0x68c800ba…fc09
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity