← previous blocknext block →recent activity
Analyzing
Block #83,642,408
38 transactions · 35 stateful · 2026-06-25 17:09:15 UTC
Parallelism
66/100
Blocked
60%
Avg conflicts / tx
1.66
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #83,642,408 · 38 txs across 13 waves · depth 13
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w110w312w013w114w215w016w118w219w326w927w428w1032w434w1135w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe99d8e68…a16e
0x34b655…2a6f
16 touches
28 conflicts
0x022f72c3…07b6
0xc8689a…ee79
10 touches
10 conflicts
0xf324b405…ca30
0x34b655…2a6f
10 touches
10 conflicts
0xbd68c7c7…40b3
0x34b655…2a6f
10 touches
10 conflicts
0xb1c67a7d…b9b1
0x34b655…2a6f
10 touches
10 conflicts
0xac0c0220…814d
0x34b655…2a6f
10 touches
10 conflicts
0x9b58e20f…2dd9
0x34b655…2a6f
10 touches
10 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 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
28 conflicts on slot 0xe99d8e683a…2ea16e
Audit this contract →
← previous block·next block →recent activity