← previous blocknext block →recent activity
Analyzing
Block #83,642,641
33 transactions · 30 stateful · 2026-06-25 17:10:48 UTC
Parallelism
58/100
Blocked
60%
Avg conflicts / tx
2.24
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,642,641 · 33 txs across 14 waves · depth 14
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w07w19w010w112w013w114w215w316w417w518w619w721w122w924w1028w830w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
18 touches
36 conflicts
0xf997c4c7…617d
0x34b655…2a6f
18 touches
36 conflicts
0x619f5683…5bd4
0x34b655…2a6f
16 touches
28 conflicts
0xa4492001…ef07
0x34b655…2a6f
16 touches
28 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
14 touches
21 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0x41f66ce6…8373
0x34b655…2a6f
12 touches
15 conflicts
0x7e6c970a…65af
0x34b655…2a6f
12 touches
15 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
36 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity