← previous blocknext block →recent activity
Analyzing
Block #84,572,988
18 transactions · 16 stateful · 2026-06-30 00:32:54 UTC
Parallelism
72/100
Blocked
44%
Avg conflicts / tx
0.61
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,572,988 · 18 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w18w010w111w112w215w216w317w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xab86573c…682e
0x34b655…2a6f
6 touches
3 conflicts
0xf1e0175c…5649
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xca3931f0…0855
0x34b655…2a6f
6 touches
3 conflicts
0x8fa4be6e…e720
0x34b655…2a6f
4 touches
1 conflict
0x9d26a04f…4842
0x34b655…2a6f
4 touches
1 conflict
0xa335f3ac…e904
0x34b655…2a6f
4 touches
1 conflict
0xb9b4eff6…c3ef
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 0xab86573c9c…f3682e
Audit this contract →
← previous block·next block →recent activity