← previous blocknext block →recent activity
Analyzing
Block #84,121,169
14 transactions · 10 stateful · 2026-06-27 22:21:24 UTC
Parallelism
86/100
Blocked
20%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,121,169 · 14 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w18w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd2cdfa3f…f071
0x34b655…2a6f
4 touches
1 conflict
0x5da4ed2f…283f
0xa6afd3…d132
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x56785e37…a197
0x065c9d…c394
2 touches
0 conflicts
0x69deb9ac…b6e4
0x065c9d…c394
2 touches
0 conflicts
0x6a712218…4c32
0x065c9d…c394
2 touches
0 conflicts
0x73508718…732f
0x065c9d…c394
2 touches
0 conflicts
0xaa4c77d3…fe14
0x065c9d…c394
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 0xd2cdfa3f93…37f071
Audit this contract →
← previous block·next block →recent activity