← previous blocknext block →recent activity
Analyzing
Block #84,253,425
17 transactions · 14 stateful · 2026-06-28 13:02:07 UTC
Parallelism
88/100
Blocked
29%
Avg conflicts / tx
0.24
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,253,425 · 17 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
4w05w16w08w09w111w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0xe27b0bdf…b21a
0x34b655…2a6f
4 touches
1 conflict
0xd025d7d7…f05a
0x3bd359…433a
4 touches
1 conflict
0x79eb41ac…d811
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0000
0x25ef1a…5bf1
2 touches
0 conflicts
0x00000000…0002
0x25ef1a…5bf1
2 touches
0 conflicts
0x00000000…0078
0x25ef1a…5bf1
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
1 conflict on slot 0x6f132c01d5…7dcdcd
Audit this contract →
← previous block·next block →recent activity