← previous blocknext block →recent activity
Analyzing
Block #83,453,101
50 transactions · 42 stateful · 2026-06-24 20:06:00 UTC
Parallelism
66/100
Blocked
74%
Avg conflicts / tx
2.64
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #83,453,101 · 50 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w17w08w010w211w312w413w514w616w717w818w920w1021w1134w835w936w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
16 touches
28 conflicts
0x37d5916a…e60c
0x34b655…2a6f
16 touches
28 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
16 touches
28 conflicts
0x763dd151…d9de
0xa6afd3…d132
14 touches
21 conflicts
0xe6950848…9ff6
0x34b655…2a6f
14 touches
21 conflicts
0x40970e69…da50
0x69df8a…6292
14 touches
21 conflicts
0x8cf3d245…1d0d
0x69df8a…6292
14 touches
21 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 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity