← previous blocknext block →recent activity
Analyzing
Block #80,824,934
15 transactions · 11 stateful · 2026-06-12 15:49:14 UTC
Parallelism
87/100
Blocked
18%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #80,824,934 · 15 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
1w02w03w113w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab4aea39…fcaa
0x34b655…2a6f
4 touches
1 conflict
0x7506443a…4820
0x34b655…2a6f
4 touches
1 conflict
0x56c10465…9f7a
0x34b655…2a6f
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x52f310b6…5be2
0x065c9d…c394
2 touches
0 conflicts
0xde44d637…bae8
0x065c9d…c394
2 touches
0 conflicts
0x1e3bca01…8e6b
0x34b655…2a6f
2 touches
0 conflicts
0x37b10c3b…8fcf
0x34b655…2a6f
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 0xab4aea3921…b6fcaa
Audit this contract →
← previous block·next block →recent activity