← previous blocknext block →recent activity
Analyzing
Block #84,363,087
17 transactions · 14 stateful · 2026-06-29 01:12:55 UTC
Parallelism
71/100
Blocked
43%
Avg conflicts / tx
0.65
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,363,087 · 17 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
2w03w14w08w09w111w214w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3ec82b22…1f46
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x3e505a15…70f8
0x34b655…2a6f
4 touches
1 conflict
0x3f7ad3a0…de3b
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x03b507c6…f4ed
0x34b655…2a6f
4 touches
1 conflict
0x166e0fd3…b4f3
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
6 conflicts on slot 0x3ec82b22de…041f46
Audit this contract →
← previous block·next block →recent activity