← previous blocknext block →recent activity
Analyzing
Block #93,229,422
14 transactions · 9 stateful · 2026-08-05 02:37:12 UTC
Parallelism
71/100
Blocked
33%
Avg conflicts / tx
0.36
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,229,422 · 14 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
3w04w18w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf738e7ab…5aec
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x00f245ce…1e10
0x34b655…2a6f
4 touches
1 conflict
0x0168ce43…cd66
0x34b655…2a6f
4 touches
1 conflict
0x14bef782…a710
0x34b655…2a6f
4 touches
1 conflict
0x42522e76…2592
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
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
1 conflict on slot 0xf738e7abcf…fb5aec
Audit this contract →
← previous block·next block →recent activity