← previous blocknext block →recent activity
Analyzing
Block #83,398,945
51 transactions · 41 stateful · 2026-06-24 14:04:13 UTC
Parallelism
73/100
Blocked
66%
Avg conflicts / tx
2.06
Longest chain
14 deep
Execution timeline
did this block parallelize well?
view
block #83,398,945 · 51 txs across 14 waves · depth 14
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w17w110w212w313w414w515w617w018w120w021w122w223w324w425w526w627w728w829w930w1039w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
24 touches
66 conflicts
0x022f72c3…07b6
0xc8689a…ee79
12 touches
15 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
12 touches
15 conflicts
0xdb13034e…be94
0x34b655…2a6f
12 touches
15 conflicts
0x9c7571b3…9605
0x34b655…2a6f
12 touches
15 conflicts
0xa1571d54…ae41
0x34b655…2a6f
12 touches
15 conflicts
0x7e6c970a…65af
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 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