← previous blocknext block →recent activity
Analyzing
Block #83,624,803
40 transactions · 33 stateful · 2026-06-25 15:11:39 UTC
Parallelism
82/100
Blocked
58%
Avg conflicts / tx
1.23
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #83,624,803 · 40 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
1w02w14w05w16w27w08w19w211w312w413w514w630w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xaa7ee7…f0e4
14 touches
21 conflicts
0x737acb78…fce8
0x34b655…2a6f
10 touches
10 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002b
0x1b6862…e19c
6 touches
3 conflicts
0x479ce48c…fa16
0x1b6862…e19c
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: 0xaa7ee7ce…aff0e4
21 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity