← previous blocknext block →recent activity
Analyzing
Block #76,436,341
11 transactions · 7 stateful · 2026-05-23 07:56:05 UTC
Parallelism
82/100
Blocked
14%
Avg conflicts / tx
0.09
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #76,436,341 · 11 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
1w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x6d2b3208…181c
0x34b655…2a6f
3 touches
1 conflict
0xf6884b1c…8b7f
0x34b655…2a6f
3 touches
1 conflict
0x100cf374…6949
0x2ab50b…5c41
2 touches
0 conflicts
0x1063339b…b9a3
0x2ab50b…5c41
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 0x9a3068dd84…9918f1
Audit this contract →
← previous block·next block →recent activity