← previous blocknext block →recent activity
Analyzing
Block #81,029,918
19 transactions · 12 stateful · 2026-06-13 14:35:27 UTC
Parallelism
68/100
Blocked
58%
Avg conflicts / tx
0.89
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #81,029,918 · 19 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w25w36w47w510w011w116w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf6476f21…3580
0x34b655…2a6f
12 touches
15 conflicts
0xd6fc419f…37ff
0x34b655…2a6f
6 touches
3 conflicts
0x5d7f309d…5145
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…153b
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…153c
0x34b655…2a6f
6 touches
3 conflicts
0x8e507257…71c1
0x34b655…2a6f
6 touches
3 conflicts
0x97d5efed…1aa4
0x34b655…2a6f
6 touches
3 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
15 conflicts on slot 0xf6476f21e7…f83580
Audit this contract →
← previous block·next block →recent activity