← previous blocknext block →recent activity
Analyzing
Block #84,362,509
9 transactions · 8 stateful · 2026-06-29 01:09:04 UTC
Parallelism
78/100
Blocked
13%
Avg conflicts / tx
0.22
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,362,509 · 9 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
4w06w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x67a0f456…07e7
0x34b655…2a6f
4 touches
1 conflict
0x7500c6c7…6b90
0x34b655…2a6f
4 touches
1 conflict
0x72a152dd…9ec4
0x16f70c…c3dd
2 touches
0 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
2 touches
0 conflicts
0x2799a4b5…20f9
0x58e158…3d57
2 touches
0 conflicts
0x3dea5c3d…5fb8
0x58e158…3d57
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity