← previous blocknext block →recent activity
Analyzing
Block #83,642,016
19 transactions · 19 stateful · 2026-06-25 17:06:38 UTC
Parallelism
74/100
Blocked
47%
Avg conflicts / tx
0.84
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,642,016 · 19 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
2w03w14w05w16w07w18w19w210w311w415w217w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x049cca71…b102
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0xec0e0220…cb90
0x34b655…2a6f
6 touches
3 conflicts
0xbb3504d4…b05f
0x34b655…2a6f
6 touches
3 conflicts
0x40619b50…0aec
0x34b655…2a6f
4 touches
1 conflict
0x415a99b6…15c7
0x34b655…2a6f
4 touches
1 conflict
0x529a94a3…ac8b
0x34b655…2a6f
4 touches
1 conflict
0x7e6c970a…65af
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 0x049cca710d…16b102
Audit this contract →
← previous block·next block →recent activity