← previous blocknext block →recent activity
Analyzing
Block #84,498,242
14 transactions · 13 stateful · 2026-06-29 16:13:57 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.29
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,498,242 · 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
1w02w03w16w09w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xa16b3e4e…0786
0x34b655…2a6f
4 touches
1 conflict
0xe2e45419…f17b
0x34b655…2a6f
4 touches
1 conflict
0x1e04c5ec…8d51
0x34b655…2a6f
2 touches
0 conflicts
0x348271ae…d949
0x34b655…2a6f
2 touches
0 conflicts
0x3dc75cca…6730
0x34b655…2a6f
2 touches
0 conflicts
0x4ae3b148…7ed2
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 0x6f132c01d5…7dcdcc
Audit this contract →
← previous block·next block →recent activity