← previous blocknext block →recent activity
Analyzing
Block #83,631,068
21 transactions · 17 stateful · 2026-06-25 15:53:28 UTC
Parallelism
76/100
Blocked
29%
Avg conflicts / tx
0.33
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,631,068 · 21 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
9w010w112w013w117w218w319w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfd4e2262…cd8c
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x2cb897e4…21ea
0x34b655…2a6f
4 touches
1 conflict
0x3710478b…a791
0x34b655…2a6f
4 touches
1 conflict
0x373ab072…fffe
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x524f0872…0d12
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 0xfd4e22625a…b8cd8c
Audit this contract →
← previous block·next block →recent activity