← previous blocknext block →recent activity
Analyzing
Block #84,280,939
17 transactions · 16 stateful · 2026-06-28 16:05:25 UTC
Parallelism
76/100
Blocked
25%
Avg conflicts / tx
0.35
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,280,939 · 17 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w18w010w111w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5bd818fc…4f86
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xe732567d…b65d
0x34b655…2a6f
6 touches
3 conflicts
0xe75cebb6…6b36
0x065c9d…c394
4 touches
1 conflict
0x03fb27fd…0c06
0x34b655…2a6f
4 touches
1 conflict
0x07f69062…03ec
0x34b655…2a6f
4 touches
1 conflict
0x3d11b39b…962c
0x34b655…2a6f
4 touches
1 conflict
0x55092e8e…37f5
0x34b655…2a6f
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
3 conflicts on slot 0x5bd818fcf8…714f86
Audit this contract →
← previous block·next block →recent activity