← previous blocknext block →recent activity
Analyzing
Block #84,499,827
16 transactions · 14 stateful · 2026-06-29 16:24:32 UTC
Parallelism
81/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,499,827 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w09w010w111w012w114w115w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0d622e34…0000
0x681e90…ae09
4 touches
1 conflict
0x42041fec…bd86
0x754704…b603
4 touches
1 conflict
0x5b33f5b9…4bab
0x34b655…2a6f
4 touches
1 conflict
0x18ab80cb…19b9
0x34b655…2a6f
2 touches
0 conflicts
0x2754e960…bcc1
0x34b655…2a6f
2 touches
0 conflicts
0x350c7a71…8d82
0x34b655…2a6f
2 touches
0 conflicts
0x3f4dc602…5a18
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity