← previous blocknext block →recent activity
Analyzing
Block #84,048,157
19 transactions · 17 stateful · 2026-06-27 14:14:55 UTC
Parallelism
84/100
Blocked
47%
Avg conflicts / tx
0.58
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,048,157 · 19 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w05w16w29w110w112w213w014w115w217w018w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb30e1191…9e3c
0x34b655…2a6f
6 touches
3 conflicts
0x42041fec…bd86
0x754704…b603
6 touches
3 conflicts
0x29686688…0598
0xa6afd3…d132
4 touches
1 conflict
0x8cf1f868…c5af
0x34b655…2a6f
4 touches
1 conflict
0x8e5cc690…b06b
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe9d2a96b…9b8b
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 0xb30e119129…4f9e3c
Audit this contract →
← previous block·next block →recent activity