← previous blocknext block →recent activity
Analyzing
Block #83,658,818
17 transactions · 16 stateful · 2026-06-25 18:58:43 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.82
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,658,818 · 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
2w03w15w16w27w312w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc8fec9ca…2d60
0x34b655…2a6f
8 touches
6 conflicts
0xed196dd4…a16b
0x34b655…2a6f
8 touches
6 conflicts
0x1175233a…64e7
0x34b655…2a6f
6 touches
3 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
6 touches
3 conflicts
0x5d7f309d…5145
0x34b655…2a6f
4 touches
1 conflict
0x63dffde1…1765
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0x9b58e20f…2dd9
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 0xc8fec9cacc…f42d60
Audit this contract →
← previous block·next block →recent activity