← previous blocknext block →recent activity
Analyzing
Block #84,574,876
8 transactions · 7 stateful · 2026-06-30 00:45:30 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #84,574,876 · 8 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
2w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb44d5376…33cc
0x34b655…2a6f
6 touches
3 conflicts
0x63da0619…7a55
0x34b655…2a6f
5 touches
3 conflicts
0x274b85f7…c526
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x374fc18a…6998
0x34b655…2a6f
2 touches
0 conflicts
0x37bc8c03…fc4c
0x34b655…2a6f
2 touches
0 conflicts
0x3817bbca…1a2e
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
3 conflicts on slot 0xb44d5376ca…0b33cc
Audit this contract →
← previous block·next block →recent activity