← previous blocknext block →recent activity
Analyzing
Block #79,420,347
23 transactions · 19 stateful · 2026-06-06 03:32:09 UTC
Parallelism
78/100
Blocked
42%
Avg conflicts / tx
0.48
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #79,420,347 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w26w37w415w319w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf853eb8e…4027
0x34b655…2a6f
6 touches
3 conflicts
0x3404afab…fcd9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x06c03b25…1ec4
0x34b655…2a6f
4 touches
1 conflict
0xae729f06…bdd0
0xa6afd3…d132
4 touches
1 conflict
0x7cbd466f…1700
0x34b655…2a6f
4 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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity