← previous blocknext block →recent activity
Analyzing
Block #83,941,583
25 transactions · 23 stateful · 2026-06-27 02:24:54 UTC
Parallelism
80/100
Blocked
48%
Avg conflicts / tx
0.72
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #83,941,583 · 25 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w28w09w110w211w312w013w114w315w016w118w319w421w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xef65bff3…7c9d
0x2a68ba…90c5
8 touches
6 conflicts
0x00000000…0002
0xd637b3…4160
8 touches
6 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x00000000…003d
0xa6afd3…d132
6 touches
3 conflicts
0x11b69a7e…334e
0xee8c0e…1242
6 touches
3 conflicts
0xb253554f…fcf0
0xa6afd3…d132
5 touches
3 conflicts
0x9672a430…3356
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 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: Kuru Exchange: MarginAccount
6 conflicts on slot 0xef65bff33c…857c9d
Audit this contract →
← previous block·next block →recent activity