← previous blocknext block →recent activity
Analyzing
Block #84,100,101
17 transactions · 12 stateful · 2026-06-27 20:01:05 UTC
Parallelism
88/100
Blocked
17%
Avg conflicts / tx
0.18
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,100,101 · 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
1w02w04w17w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xb3572c95…9c4a
0x2a68ba…90c5
4 touches
1 conflict
0x505f101e…7ad6
0x34b655…2a6f
4 touches
1 conflict
0x729c91b8…9538
0x188d58…ea8e
2 touches
0 conflicts
0x019ded9d…6fa0
0x34b655…2a6f
2 touches
0 conflicts
0x08870c82…be84
0x34b655…2a6f
2 touches
0 conflicts
0x08e8f2c9…a11a
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 0xab86573c9c…f3682e
Audit this contract →
← previous block·next block →recent activity