← previous blocknext block →recent activity
Analyzing
Block #92,601,457
15 transactions · 14 stateful · 2026-08-02 21:55:50 UTC
Parallelism
73/100
Blocked
36%
Avg conflicts / tx
0.53
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #92,601,457 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w04w05w17w28w39w110w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x86b6d4a1…728c
0x34b655…2a6f
6 touches
3 conflicts
0x1efc452b…354f
0x34b655…2a6f
4 touches
1 conflict
0x1efc452b…3550
0x34b655…2a6f
4 touches
1 conflict
0x6bdd6387…7ffa
0x34b655…2a6f
4 touches
1 conflict
0x6e0ad8aa…9086
0x34b655…2a6f
4 touches
1 conflict
0x803eb45d…00bd
0x34b655…2a6f
4 touches
1 conflict
0x966e45cf…0f25
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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: Perpl
3 conflicts on slot 0x86b6d4a127…d9728c
Audit this contract →
← previous block·next block →recent activity