← previous blocknext block →recent activity
Analyzing
Block #84,572,093
7 transactions · 6 stateful · 2026-06-30 00:26:56 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.43
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #84,572,093 · 7 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
1w02w03w16w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6f132c01…cdcd
0x34b655…2a6f
4 touches
1 conflict
0x2b111712…0e59
0x34b655…2a6f
4 touches
1 conflict
0x05a7428b…ddf3
0x34b655…2a6f
4 touches
1 conflict
0x4c525ebf…dfe2
0x34b655…2a6f
4 touches
1 conflict
0x086db8fc…0024
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x39931443…c31d
0x34b655…2a6f
2 touches
0 conflicts
0x3f75fb9e…0d2e
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…7dcdcd
Audit this contract →
← previous block·next block →recent activity