← previous blocknext block →recent activity
Analyzing
Block #80,218,952
19 transactions · 17 stateful · 2026-06-09 20:28:29 UTC
Parallelism
84/100
Blocked
24%
Avg conflicts / tx
0.26
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,218,952 · 19 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
1w02w13w04w25w010w115w016w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x7d42dc8b…fdb6
0x2a68ba…90c5
4 touches
1 conflict
0x00e7cb90…5b95
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x6d383d1f…a65e
0x2a68ba…90c5
2 touches
1 conflict
0xfb64e9ec…34fd
0x2a68ba…90c5
2 touches
1 conflict
0x5cc231f5…f1cd
0x69df8a…6292
2 touches
0 conflicts
0xb05cd4f5…73d0
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity