← previous blocknext block →recent activity
Analyzing
Block #83,617,308
53 transactions · 48 stateful · 2026-06-25 14:21:30 UTC
Parallelism
64/100
Blocked
65%
Avg conflicts / tx
3.08
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #83,617,308 · 53 txs across 19 waves · depth 19
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
wave w17
wave w18
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w18w09w110w211w314w015w116w217w318w419w520w621w722w823w924w1025w1145w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0x00000000…0003
0x019883…2a9a
18 touches
36 conflicts
0x44ad89ba…cf83
0x0cc9b2…7777
18 touches
36 conflicts
0x99a3a7c1…1e2b
0x0cc9b2…7777
18 touches
36 conflicts
0x00000000…0000
0x019883…2a9a
18 touches
36 conflicts
0xa472d565…9fe4
0x3bd359…433a
18 touches
36 conflicts
0x00000000…0002
0x019883…2a9a
18 touches
36 conflicts
0xa10c86f8…4b74
0x3bd359…433a
18 touches
36 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
66 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity