← previous blocknext block →recent activity
Analyzing
Block #93,561,387
13 transactions · 13 stateful · 2026-08-06 06:26:10 UTC
Parallelism
69/100
Blocked
38%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,561,387 · 13 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
1w02w16w17w28w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ec95f2b…f4d7
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x91b0f8ed…6bd7
0x34b655…2a6f
4 touches
1 conflict
0x1bf8d2af…d140
0x34b655…2a6f
4 touches
1 conflict
0xaa6a7936…3f64
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x028b0d27…dd76
0x34b655…2a6f
4 touches
1 conflict
0x52b477bc…7ccf
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 0x8ec95f2b0e…b0f4d7
Audit this contract →
← previous block·next block →recent activity