← previous blocknext block →recent activity
Analyzing
Block #93,327,514
12 transactions · 12 stateful · 2026-08-05 10:50:24 UTC
Parallelism
67/100
Blocked
42%
Avg conflicts / tx
0.75
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,327,514 · 12 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
2w04w15w26w39w210w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x861e5aef…d32c
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x43e3decb…be40
0x34b655…2a6f
4 touches
1 conflict
0xf18f246b…fdbc
0x34b655…2a6f
4 touches
1 conflict
0x2d394d9a…5e85
0x34b655…2a6f
4 touches
1 conflict
0xa1571d54…ae41
0x34b655…2a6f
4 touches
1 conflict
0xac3e4969…39e9
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6425
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
6 conflicts on slot 0x861e5aeffa…5cd32c
Audit this contract →
← previous block·next block →recent activity