← previous blocknext block →recent activity
Analyzing
Block #81,482,284
33 transactions · 23 stateful · 2026-06-15 16:48:32 UTC
Parallelism
85/100
Blocked
39%
Avg conflicts / tx
0.55
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #81,482,284 · 33 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w08w110w011w012w113w016w118w221w022w126w227w230w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa7013be2…c0a8
0x34b655…2a6f
10 touches
10 conflicts
0xf6dfaa05…2749
0x34b655…2a6f
8 touches
6 conflicts
0xa3ff1ab2…8ae3
0x34b655…2a6f
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x1cda18d5…31c3
0x34b655…2a6f
6 touches
3 conflicts
0xf6476f21…3580
0x34b655…2a6f
6 touches
3 conflicts
0x6015ffdd…9b8d
0xd32edf…ff58
5 touches
3 conflicts
0x60ad7285…2ca5
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 0xa7013be2a1…9ac0a8
Audit this contract →
← previous block·next block →recent activity