← previous blocknext block →recent activity
Analyzing
Block #80,511,197
18 transactions · 14 stateful · 2026-06-11 04:56:01 UTC
Parallelism
78/100
Blocked
29%
Avg conflicts / tx
0.22
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,511,197 · 18 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
1w02w13w26w38w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x86e6cece…1fd5
0x2a68ba…90c5
3 touches
1 conflict
0x487d2922…28b6
0x754704…b603
2 touches
1 conflict
0x332c3caf…dcf6
0x065c9d…c394
2 touches
0 conflicts
0x4044ec23…b25d
0x065c9d…c394
2 touches
0 conflicts
0x8936fff9…c8e5
0x065c9d…c394
2 touches
0 conflicts
0x8f83230a…1a0e
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 0x8b305a3b6b…0c1c35
Audit this contract →
← previous block·next block →recent activity