← previous blocknext block →recent activity
Analyzing
Block #82,390,932
25 transactions · 19 stateful · 2026-06-19 21:47:51 UTC
Parallelism
84/100
Blocked
42%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #82,390,932 · 25 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
1w02w03w04w06w17w08w111w112w013w114w215w317w121w022w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xea1b8c07…b969
0x34b655…2a6f
6 touches
3 conflicts
0x4d0f1fa1…fd33
0x34b655…2a6f
4 touches
1 conflict
0x6836c701…a656
0x34b655…2a6f
4 touches
1 conflict
0xbac95d1b…de75
0x34b655…2a6f
4 touches
1 conflict
0xd5abc901…166d
0x34b655…2a6f
4 touches
1 conflict
0xe283e878…7262
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
6 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity