← previous blocknext block →recent activity
Analyzing
Block #80,275,800
14 transactions · 13 stateful · 2026-06-10 02:47:31 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,275,800 · 14 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w210w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5a19ef35…dc70
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfb64e9ec…34fd
0x2a68ba…90c5
2 touches
1 conflict
0x305eac8d…6245
0x065c9d…c394
2 touches
0 conflicts
0x5b60f172…2ff1
0x065c9d…c394
2 touches
0 conflicts
0xf339dca6…acde
0x065c9d…c394
2 touches
0 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
2 touches
0 conflicts
0x01a89030…f786
0x368ee5…7ca4
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 0x5a19ef3589…3ddc70
Audit this contract →
← previous block·next block →recent activity