← previous blocknext block →recent activity
Analyzing
Block #84,511,995
20 transactions · 18 stateful · 2026-06-29 17:45:44 UTC
Parallelism
65/100
Blocked
61%
Avg conflicts / tx
1.6
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #84,511,995 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w16w27w38w49w513w414w215w516w617w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xacbc3fbb…fe8e
0x34b655…2a6f
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0xe02484a6…c32e
0xc8689a…ee79
6 touches
3 conflicts
0x06e5b3c6…913f
0x34b655…2a6f
6 touches
3 conflicts
0x6e2becf4…0c5f
0x34b655…2a6f
6 touches
3 conflicts
0x94710b77…a921
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 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
15 conflicts on slot 0xacbc3fbbbb…75fe8e
Audit this contract →
← previous block·next block →recent activity