← previous blocknext block →recent activity
Analyzing
Block #83,655,070
17 transactions · 17 stateful · 2026-06-25 18:33:44 UTC
Parallelism
59/100
Blocked
47%
Avg conflicts / tx
1
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,655,070 · 17 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w17w28w310w011w412w313w414w515w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1c48b3ac…a03c
0x34b655…2a6f
8 touches
6 conflicts
0x46d5a052…ff2e
0x34b655…2a6f
8 touches
6 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x216b4ce7…2b99
0x34b655…2a6f
6 touches
3 conflicts
0x6ac6d1bf…8b19
0x34b655…2a6f
6 touches
3 conflicts
0xaa1ab77f…8a92
0x34b655…2a6f
6 touches
3 conflicts
0xd064a456…b881
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x1c48b3acf3…40a03c
Audit this contract →
← previous block·next block →recent activity