← previous blocknext block →recent activity
Analyzing
Block #83,876,460
17 transactions · 16 stateful · 2026-06-26 19:10:52 UTC
Parallelism
76/100
Blocked
44%
Avg conflicts / tx
0.47
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #83,876,460 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w15w06w17w08w19w210w311w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3975d93…b4a2
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x90a9e3f8…17ab
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xe2ec0e6c…269c
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
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
3 conflicts on slot 0xb3975d9364…28b4a2
Audit this contract →
← previous block·next block →recent activity