← previous blocknext block →recent activity
Analyzing
Block #84,620,827
14 transactions · 12 stateful · 2026-06-30 05:51:35 UTC
Parallelism
86/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,620,827 · 14 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
5w06w08w19w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xa16b3e4e…0787
0x34b655…2a6f
4 touches
1 conflict
0xab86573c…682e
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x2d69c1bb…6b5e
0x34b655…2a6f
4 touches
1 conflict
0x4a2b6cf1…3123
0x754704…b603
2 touches
0 conflicts
0x7d8a115c…35b2
0x754704…b603
2 touches
0 conflicts
0x01a89030…f786
0x98dc6e…8633
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 0xa16b3e4e62…240787
Audit this contract →
← previous block·next block →recent activity