← previous blocknext block →recent activity
Analyzing
Block #84,041,950
17 transactions · 14 stateful · 2026-06-27 13:33:38 UTC
Parallelism
88/100
Blocked
14%
Avg conflicts / tx
0.12
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,041,950 · 17 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
5w06w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1b6e8fc2…73d4
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0xe99d8e68…a16e
0x34b655…2a6f
4 touches
1 conflict
0x62d6e82b…a750
0x34b655…2a6f
2 touches
0 conflicts
0x66e47d07…baa6
0x34b655…2a6f
2 touches
0 conflicts
0x6f6fc26c…3e34
0x34b655…2a6f
2 touches
0 conflicts
0x8726ff39…3be8
0x34b655…2a6f
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 0x1b6e8fc296…6073d4
Audit this contract →
← previous block·next block →recent activity