← previous blocknext block →recent activity
Analyzing
Block #83,637,142
44 transactions · 35 stateful · 2026-06-25 16:34:05 UTC
Parallelism
68/100
Blocked
71%
Avg conflicts / tx
1.95
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,637,142 · 44 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
1w07w08w19w210w312w417w018w119w221w422w523w624w725w826w929w130w533w634w1035w138w839w940w1041w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0xd7add284…8d28
0x34b655…2a6f
10 touches
10 conflicts
0x98d3fc79…df78
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0x5f3fc680…f989
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity