← previous blocknext block →recent activity
Analyzing
Block #83,653,191
60 transactions · 46 stateful · 2026-06-25 18:21:15 UTC
Parallelism
67/100
Blocked
76%
Avg conflicts / tx
3.07
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #83,653,191 · 60 txs across 20 waves · depth 20
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
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w05w16w29w312w015w118w219w320w421w523w024w125w250w652w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
30 touches
105 conflicts
0xd2cdfa3f…f071
0x34b655…2a6f
14 touches
21 conflicts
0x3cf50d44…961b
0x34b655…2a6f
12 touches
15 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x785889c9…0603
0x34b655…2a6f
12 touches
15 conflicts
0x3e776e71…4bbf
0x34b655…2a6f
12 touches
15 conflicts
0xd98b3c10…67b8
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
105 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity