← previous blocknext block →recent activity
Analyzing
Block #84,349,932
17 transactions · 16 stateful · 2026-06-28 23:45:07 UTC
Parallelism
71/100
Blocked
50%
Avg conflicts / tx
0.76
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #84,349,932 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w06w17w08w09w110w211w113w114w215w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x8f4c5cb2…cbee
0x34b655…2a6f
6 touches
3 conflicts
0x2754e960…bcc1
0x34b655…2a6f
6 touches
3 conflicts
0x03b4fefa…9a00
0x34b655…2a6f
4 touches
1 conflict
0x403d1735…de44
0x34b655…2a6f
4 touches
1 conflict
0x4bdcc5ee…7e90
0x34b655…2a6f
4 touches
1 conflict
0x7a247673…6c5b
0x34b655…2a6f
4 touches
1 conflict
0x81e1f4e8…08d7
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
6 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity