← previous blocknext block →recent activity
Analyzing
Block #80,246,973
21 transactions · 18 stateful · 2026-06-09 23:35:20 UTC
Parallelism
90/100
Blocked
28%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,246,973 · 21 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
1w02w15w06w18w116w018w119w020w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa3ff1ab2…8ae3
0x34b655…2a6f
4 touches
1 conflict
0x92339d95…0800
0x0000a8…8888
4 touches
1 conflict
0x00000000…003d
0xa6afd3…d132
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x8b305a3b…1c35
0x34b655…2a6f
4 touches
1 conflict
0x80afd9d9…57cf
0x065c9d…c394
2 touches
0 conflicts
0xbee4f495…b69e
0x065c9d…c394
2 touches
0 conflicts
0x25d74ecf…d999
0x1efe02…37d6
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 0xa3ff1ab2e8…2a8ae3
Audit this contract →
← previous block·next block →recent activity