← previous blocknext block →recent activity
Analyzing
Block #84,359,761
21 transactions · 14 stateful · 2026-06-29 00:50:45 UTC
Parallelism
81/100
Blocked
21%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,359,761 · 21 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
7w014w015w117w218w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x75cdffd8…c217
0x34b655…2a6f
6 touches
3 conflicts
0x3b4b5b0a…a8d9
0x34b655…2a6f
4 touches
1 conflict
0x0d2e1791…c1dd
0x34b655…2a6f
4 touches
1 conflict
0x98d3fc79…df78
0x34b655…2a6f
4 touches
1 conflict
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0xc5e17fca…f34a
0x34b655…2a6f
4 touches
1 conflict
0x97ea91d9…00b5
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity