← previous blocknext block →recent activity
Analyzing
Block #84,330,212
14 transactions · 12 stateful · 2026-06-28 21:33:44 UTC
Parallelism
79/100
Blocked
25%
Avg conflicts / tx
0.29
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,330,212 · 14 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
1w02w110w011w113w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x5d82c9b5…004c
0x3bd359…433a
4 touches
1 conflict
0x00000000…0004
0x5afd3e…7620
4 touches
1 conflict
0x06ba83ca…9a08
0x5afd3e…7620
4 touches
1 conflict
0x22720302…2eaf
0x5afd3e…7620
4 touches
1 conflict
0x450cb620…65b1
0x5afd3e…7620
4 touches
1 conflict
0x72870ca3…6e39
0x5afd3e…7620
4 touches
1 conflict
0x404314de…df1a
0x8b0d32…7367
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…7dcdcd
Audit this contract →
← previous block·next block →recent activity