← previous blocknext block →recent activity
Analyzing
Block #83,454,812
23 transactions · 19 stateful · 2026-06-24 20:17:27 UTC
Parallelism
70/100
Blocked
58%
Avg conflicts / tx
0.91
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,454,812 · 23 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
1w02w13w26w07w18w29w010w111w313w414w217w520w521w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbfe63d66…c3e6
0x34b655…2a6f
8 touches
6 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
8 touches
6 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
6 touches
3 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xd16df6cd…5532
0x40c49f…2af0
6 touches
3 conflicts
0x47c7f270…6b00
0x34b655…2a6f
4 touches
1 conflict
0x5bdb0bbb…f5a2
0x34b655…2a6f
4 touches
1 conflict
0x03fb27fd…0c06
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
6 conflicts on slot 0xbfe63d66dd…96c3e6
Audit this contract →
← previous block·next block →recent activity