← previous blocknext block →recent activity
Analyzing
Block #83,453,473
30 transactions · 24 stateful · 2026-06-24 20:08:30 UTC
Parallelism
70/100
Blocked
71%
Avg conflicts / tx
2
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #83,453,473 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w17w29w312w013w114w215w316w417w518w619w720w821w326w127w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
18 touches
36 conflicts
0x2e72f452…bd7a
0x34b655…2a6f
12 touches
15 conflicts
0xa9988419…9f45
0x34b655…2a6f
8 touches
6 conflicts
0xe1593d74…b99c
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x31aa2853…8dbb
0xc8689a…ee79
8 touches
6 conflicts
0xe6950848…9ff6
0x34b655…2a6f
6 touches
3 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 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