← previous blocknext block →recent activity
Analyzing
Block #79,408,203
27 transactions · 23 stateful · 2026-06-06 02:11:10 UTC
Parallelism
70/100
Blocked
39%
Avg conflicts / tx
1.19
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #79,408,203 · 27 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w08w113w014w217w018w119w220w321w422w523w624w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xaa0d0542…d8ec
0x34b655…2a6f
6 touches
3 conflicts
0x3404afab…fcd9
0x34b655…2a6f
6 touches
3 conflicts
0x91b02220…68f6
0x34b655…2a6f
6 touches
3 conflicts
0xf853eb8e…4027
0x34b655…2a6f
6 touches
3 conflicts
0x5540f956…69e8
0x065c9d…c394
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0xbb12db23…857e
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity