← previous blocknext block →recent activity
Analyzing
Block #83,453,155
46 transactions · 41 stateful · 2026-06-24 20:06:22 UTC
Parallelism
59/100
Blocked
83%
Avg conflicts / tx
4.74
Longest chain
19 deep
Execution timeline
did this block parallelize well?
view
block #83,453,155 · 46 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
1w02w03w14w26w17w18w29w310w411w512w613w714w815w916w1018w1119w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
32 touches
120 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
24 touches
66 conflicts
0xbeb10b8a…4ce5
0x34b655…2a6f
18 touches
36 conflicts
0xe02484a6…c32e
0xc8689a…ee79
16 touches
28 conflicts
0xef65bff3…7c9d
0x2a68ba…90c5
16 touches
28 conflicts
0xbfca3cd0…5023
0x34b655…2a6f
16 touches
28 conflicts
0xb5c4826d…bdd6
0x69df8a…6292
16 touches
28 conflicts
0xb8fccd1b…b5f2
0x69df8a…6292
16 touches
28 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
120 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity