← previous blocknext block →recent activity
Analyzing
Block #84,255,155
31 transactions · 28 stateful · 2026-06-28 13:13:38 UTC
Parallelism
87/100
Blocked
46%
Avg conflicts / tx
0.52
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #84,255,155 · 31 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w04w05w18w09w110w011w113w016w220w121w222w225w126w127w228w329w130w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xc47ca59a…b171
0x34b655…2a6f
6 touches
3 conflicts
0x38ec2c24…ef42
0x34b655…2a6f
6 touches
3 conflicts
0xde2b702b…b081
0xd32edf…ff58
5 touches
3 conflicts
0x033ddbe8…850a
0x34b655…2a6f
4 touches
1 conflict
0x07bb3f5a…617e
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0xbcbe3e05…dfc4
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
3 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity