← previous blocknext block →recent activity
Analyzing
Block #83,029,005
25 transactions · 19 stateful · 2026-06-22 20:51:30 UTC
Parallelism
72/100
Blocked
63%
Avg conflicts / tx
1.48
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,029,005 · 25 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w16w27w38w49w513w014w115w216w317w418w519w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x08913286…f0df
0x34b655…2a6f
14 touches
21 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0xdf708ee7…1fcf
0xc8689a…ee79
10 touches
10 conflicts
0xab83f300…f8c8
0x34b655…2a6f
10 touches
10 conflicts
0xfcb9138a…3830
0xc8689a…ee79
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0x664bf99e…0a8c
0x34b655…2a6f
10 touches
10 conflicts
0xb624d2ea…8c87
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
21 conflicts on slot 0x08913286f9…0ff0df
Audit this contract →
← previous block·next block →recent activity