← previous blocknext block →recent activity
Analyzing
Block #84,523,826
8 transactions · 8 stateful · 2026-06-29 19:04:36 UTC
Parallelism
38/100
Blocked
50%
Avg conflicts / tx
0.5
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,523,826 · 8 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w26w37w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0xc47ca59a…b171
0x34b655…2a6f
4 touches
1 conflict
0xd597209e…9800
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0110331c…b891
0x34b655…2a6f
4 touches
1 conflict
0x3a3ae0e3…ac9b
0x34b655…2a6f
4 touches
1 conflict
0x00000000…001d
0x1b6862…e19c
2 touches
0 conflicts
0x00000000…002d
0x1b6862…e19c
2 touches
0 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
1 conflict on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity