← previous blocknext block →recent activity
Analyzing
Block #84,493,911
10 transactions · 10 stateful · 2026-06-29 15:45:04 UTC
Parallelism
60/100
Blocked
30%
Avg conflicts / tx
0.6
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,493,911 · 10 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w18w29w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x6a53b1c0…c3f2
0x34b655…2a6f
4 touches
1 conflict
0x7fa1794c…3323
0x34b655…2a6f
4 touches
1 conflict
0xd469b0e6…4542
0x065c9d…c394
2 touches
0 conflicts
0xe421bd48…96ed
0x065c9d…c394
2 touches
0 conflicts
0xf103a7d8…badb
0x065c9d…c394
2 touches
0 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity