← previous blocknext block →recent activity
Analyzing
Block #94,816,552
17 transactions · 16 stateful · 2026-08-10 15:56:16 UTC
Parallelism
59/100
Blocked
44%
Avg conflicts / tx
0.82
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #94,816,552 · 17 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
2w03w04w15w28w09w311w412w513w616w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd76a03c0…e690
0x34b655…2a6f
6 touches
3 conflicts
0xa3a621f8…75a2
0x34b655…2a6f
6 touches
3 conflicts
0x4329bae0…29f9
0x34b655…2a6f
6 touches
3 conflicts
0xd3b0a558…1513
0x34b655…2a6f
6 touches
3 conflicts
0x734ee320…caae
0x34b655…2a6f
4 touches
1 conflict
0x7e5ea60a…c4aa
0x34b655…2a6f
4 touches
1 conflict
0x92132ed7…2722
0x34b655…2a6f
4 touches
1 conflict
0x92385428…6941
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 0xd76a03c049…7ee690
Audit this contract →
← previous block·next block →recent activity