← previous blocknext block →recent activity
Analyzing
Block #80,165,150
13 transactions · 10 stateful · 2026-06-09 14:29:36 UTC
Parallelism
85/100
Blocked
20%
Avg conflicts / tx
0.31
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,165,150 · 13 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
2w03w04w06w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0bca06cc…b10d
0x065c9d…c394
3 touches
1 conflict
0x2acfa091…d7e4
0x065c9d…c394
3 touches
1 conflict
0x0776df79…5e90
0x065c9d…c394
3 touches
1 conflict
0x0776df79…5e91
0x065c9d…c394
3 touches
1 conflict
0xc6793074…f7d2
0x065c9d…c394
3 touches
1 conflict
0x00000000…0005
0x5e60bc…fe22
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