← previous blocknext block →recent activity
Analyzing
Block #83,655,106
8 transactions · 7 stateful · 2026-06-25 18:33:58 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #83,655,106 · 8 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
1w05w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6713b018…05f3
0x34b655…2a6f
4 touches
1 conflict
0xffc2f21e…b393
0x34b655…2a6f
4 touches
1 conflict
0x09000000…0007
0x000000…1000
2 touches
0 conflicts
0x1d351a9b…f2dd
0x34b655…2a6f
2 touches
0 conflicts
0x25d69b88…a8a3
0x34b655…2a6f
2 touches
0 conflicts
0x4383029f…f951
0x34b655…2a6f
2 touches
0 conflicts
0x502ac45c…16d4
0x34b655…2a6f
2 touches
0 conflicts
0x544b22cb…7c53
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
1 conflict on slot 0x6713b0185b…1305f3
Audit this contract →
← previous block·next block →recent activity