← previous blocknext block →recent activity
Analyzing
Block #84,265,154
12 transactions · 12 stateful · 2026-06-28 14:20:17 UTC
Parallelism
83/100
Blocked
8%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,265,154 · 12 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
2w08w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0x055a7943…c67a
0x34b655…2a6f
3 touches
1 conflict
0xe7f4563f…1e58
0x34b655…2a6f
3 touches
1 conflict
0x4456c626…15f2
0x065c9d…c394
2 touches
0 conflicts
0x75da5401…e867
0x065c9d…c394
2 touches
0 conflicts
0xd228aa40…cbee
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 0x6f132c01d5…7dcdcc
Audit this contract →
← previous block·next block →recent activity