← previous blocknext block →recent activity
Analyzing
Block #80,954,558
16 transactions · 13 stateful · 2026-06-13 06:13:38 UTC
Parallelism
75/100
Blocked
23%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,954,558 · 16 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
10w011w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xe732567d…b65d
0x34b655…2a6f
4 touches
1 conflict
0x0ad4dbe8…ae93
0x34b655…2a6f
4 touches
1 conflict
0x76fc4c39…1659
0x34b655…2a6f
3 touches
1 conflict
0x15c9b5bf…f732
0x34b655…2a6f
2 touches
0 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
2 touches
0 conflicts
0x482471ad…122f
0x34b655…2a6f
2 touches
0 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity