← previous blocknext block →recent activity
Analyzing
Block #80,328,349
16 transactions · 10 stateful · 2026-06-10 08:37:52 UTC
Parallelism
88/100
Blocked
10%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,328,349 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
14w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6637e421…af93
0x34b655…2a6f
4 touches
1 conflict
0xb8228d38…3953
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0x21898044…a071
0x065c9d…c394
2 touches
0 conflicts
0x4ea2d989…1620
0x065c9d…c394
2 touches
0 conflicts
0x5729e383…3818
0x065c9d…c394
2 touches
0 conflicts
0x6358a3c9…f0fd
0x065c9d…c394
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 0x6637e421bf…b0af93
Audit this contract →
← previous block·next block →recent activity