← previous blocknext block →recent activity
Analyzing
Block #80,164,542
27 transactions · 19 stateful · 2026-06-09 14:25:33 UTC
Parallelism
85/100
Blocked
26%
Avg conflicts / tx
0.19
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,164,542 · 27 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w113w214w015w016w117w318w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x1c912a68…3b21
0x2a68ba…90c5
4 touches
1 conflict
0x057f9cf9…41fd
0x851145…3f07
3 touches
1 conflict
0xb9061b68…5922
0xd32edf…ff58
3 touches
1 conflict
0xb182933f…46ed
0x754704…b603
2 touches
1 conflict
0x4dd1db39…a995
0x188d58…ea8e
2 touches
0 conflicts
0xf6cc7de8…0b4a
0x3bd359…433a
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 0x22e0cc1d4a…90ad04
Audit this contract →
← previous block·next block →recent activity