← previous blocknext block →recent activity
Analyzing
Block #80,794,698
17 transactions · 15 stateful · 2026-06-12 12:27:36 UTC
Parallelism
82/100
Blocked
33%
Avg conflicts / tx
0.35
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #80,794,698 · 17 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
1w02w03w14w15w26w015w116w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x7fa3e5b2…f09d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x6b47245e…a342
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0x3c9bce0e…0440
0x34b655…2a6f
4 touches
1 conflict
0xa9b5baf1…186c
0x065c9d…c394
3 touches
1 conflict
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 0x7fa3e5b246…33f09d
Audit this contract →
← previous block·next block →recent activity