← previous blocknext block →recent activity
Analyzing
Block #83,467,478
21 transactions · 16 stateful · 2026-06-24 21:42:04 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.81
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #83,467,478 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w16w07w111w214w115w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x24afc70d…36ef
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x59251746…b1b7
0x34b655…2a6f
4 touches
1 conflict
0x6cdd3195…404f
0x34b655…2a6f
4 touches
1 conflict
0x9610cea3…6614
0x34b655…2a6f
4 touches
1 conflict
0xa0f5612a…9804
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity