← previous blocknext block →recent activity
Analyzing
Block #84,105,445
15 transactions · 12 stateful · 2026-06-27 20:36:39 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.27
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,105,445 · 15 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
1w06w18w212w013w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0d35e1ad…b4d6
0x34b655…2a6f
4 touches
1 conflict
0x1d3b9dd6…9681
0x34b655…2a6f
4 touches
1 conflict
0x39759403…7896
0x34b655…2a6f
4 touches
1 conflict
0x5a30d8a9…f768
0x34b655…2a6f
4 touches
1 conflict
0x672fd8ba…9e9e
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x53bca1a6…0b31
0x065c9d…c394
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
1 conflict on slot 0x0d35e1ad50…a7b4d6
Audit this contract →
← previous block·next block →recent activity