← previous blocknext block →recent activity
Analyzing
Block #83,843,349
13 transactions · 12 stateful · 2026-06-26 15:29:58 UTC
Parallelism
77/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,843,349 · 13 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
2w03w17w010w011w112w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x7cb1d883…dc23
0x34b655…2a6f
4 touches
1 conflict
0xc47ca59a…b171
0x34b655…2a6f
4 touches
1 conflict
0x00000000…0002
0xd637b3…4160
4 touches
1 conflict
0x33c14175…fca1
0x34b655…2a6f
2 touches
0 conflicts
0x3c071399…4759
0x34b655…2a6f
2 touches
0 conflicts
0x3e2c977f…ebec
0x34b655…2a6f
2 touches
0 conflicts
0x5b33f5b9…4bab
0x34b655…2a6f
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity