← previous blocknext block →recent activity
Analyzing
Block #83,637,111
21 transactions · 17 stateful · 2026-06-25 16:33:53 UTC
Parallelism
86/100
Blocked
18%
Avg conflicts / tx
0.14
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,637,111 · 21 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w016w220w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9ac79c76…c4a9
0x34b655…2a6f
4 touches
1 conflict
0x3d1bf6c2…b168
0x065c9d…c394
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x0b16149e…7d4d
0x065c9d…c394
4 touches
1 conflict
0xff96dc9b…93d7
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x502406af…e517
0x065c9d…c394
3 touches
1 conflict
0x87382912…1b69
0x065c9d…c394
3 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
1 conflict on slot 0x9ac79c76e2…88c4a9
Audit this contract →
← previous block·next block →recent activity