← previous blocknext block →recent activity
Analyzing
Block #80,218,949
18 transactions · 14 stateful · 2026-06-09 20:28:27 UTC
Parallelism
89/100
Blocked
21%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,218,949 · 18 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
2w05w06w17w08w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0xc38151f2…2bcb
0xc8689a…ee79
4 touches
1 conflict
0x1fd7e163…c544
0x065c9d…c394
2 touches
0 conflicts
0x45ea997c…467b
0x065c9d…c394
2 touches
0 conflicts
0x4d22a2b3…a080
0x065c9d…c394
2 touches
0 conflicts
0x652b0cc3…2aed
0x065c9d…c394
2 touches
0 conflicts
0x81c6c16e…1173
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 0x90f07a4ff9…b3d932
Audit this contract →
← previous block·next block →recent activity