← previous blocknext block →recent activity
Analyzing
Block #80,102,083
17 transactions · 13 stateful · 2026-06-09 07:29:32 UTC
Parallelism
76/100
Blocked
31%
Avg conflicts / tx
0.24
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #80,102,083 · 17 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
1w02w13w25w37w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x90f07a4f…d932
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
0xfd2f31c2…c1db
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
2 touches
0 conflicts
0x40970e69…da50
0x69df8a…6292
2 touches
0 conflicts
0x5cc231f5…f1cd
0x69df8a…6292
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