← previous blocknext block →recent activity
Analyzing
Block #81,030,668
26 transactions · 13 stateful · 2026-06-13 14:40:27 UTC
Parallelism
73/100
Blocked
46%
Avg conflicts / tx
0.81
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #81,030,668 · 26 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
5w07w111w214w315w416w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
14 touches
21 conflicts
0xa1571d54…ae41
0x34b655…2a6f
6 touches
3 conflicts
0x119051fe…1cb9
0x34b655…2a6f
6 touches
3 conflicts
0x217bd767…b79e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x33f2d9b1…b689
0x34b655…2a6f
4 touches
1 conflict
0x404120f4…fbaa
0x34b655…2a6f
4 touches
1 conflict
0x5d7f309d…5145
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
21 conflicts on slot 0xf6476f21e7…f83580
Audit this contract →
← previous block·next block →recent activity