← previous blocknext block →recent activity
Analyzing
Block #81,030,434
17 transactions · 11 stateful · 2026-06-13 14:38:53 UTC
Parallelism
53/100
Blocked
64%
Avg conflicts / tx
1.59
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #81,030,434 · 17 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w26w38w49w510w613w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
14 touches
21 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
14 touches
21 conflicts
0x5d7f309d…5145
0x34b655…2a6f
12 touches
15 conflicts
0xd6fc419f…37ff
0x34b655…2a6f
12 touches
15 conflicts
0xec71a70e…13ed
0x34b655…2a6f
12 touches
15 conflicts
0xa1571d54…ae41
0x34b655…2a6f
8 touches
6 conflicts
0xfaf22814…27c8
0x34b655…2a6f
4 touches
1 conflict
0x1dd11cac…7764
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