← previous blocknext block →recent activity
Analyzing
Block #83,642,627
15 transactions · 12 stateful · 2026-06-25 17:10:42 UTC
Parallelism
80/100
Blocked
25%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,642,627 · 15 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
1w02w13w08w010w113w014w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xffc2f21e…b393
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x4388045a…c325
0x065c9d…c394
2 touches
0 conflicts
0x5521cf6b…1ebe
0x065c9d…c394
2 touches
0 conflicts
0xb974ef6b…8ca5
0x065c9d…c394
2 touches
0 conflicts
0x00000000…003d
0x40c49f…2af0
2 touches
0 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
3 conflicts on slot 0xffc2f21efe…ecb393
Audit this contract →
← previous block·next block →recent activity