← previous blocknext block →recent activity
Analyzing
Block #79,414,120
32 transactions · 25 stateful · 2026-06-06 02:50:39 UTC
Parallelism
88/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #79,414,120 · 32 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w18w09w110w211w012w013w118w121w226w027w128w229w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xeeb38aa7…8f00
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x9ff176a9…152e
0x065c9d…c394
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xe560375e…4626
0x34b655…2a6f
6 touches
3 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xeeb38aa7fa…fa8f00
Audit this contract →
← previous block·next block →recent activity