← previous blocknext block →recent activity
Analyzing
Block #93,387,520
17 transactions · 16 stateful · 2026-08-05 15:52:07 UTC
Parallelism
71/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,387,520 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w04w15w27w28w113w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0e246445…9e0e
0x34b655…2a6f
6 touches
5 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x3727225e…a3cf
0x34b655…2a6f
5 touches
3 conflicts
0x733a5000…6e67
0x34b655…2a6f
5 touches
3 conflicts
0x34d95d94…3a16
0x34b655…2a6f
4 touches
1 conflict
0x43ade79a…fab9
0x34b655…2a6f
4 touches
1 conflict
0x013d7988…5064
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
5 conflicts on slot 0x0e2464459c…149e0e
Audit this contract →
← previous block·next block →recent activity