← previous blocknext block →recent activity
Analyzing
Block #93,248,014
6 transactions · 6 stateful · 2026-08-05 04:10:41 UTC
Parallelism
50/100
Blocked
33%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,248,014 · 6 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x040ffbf2…b9fd
0x34b655…2a6f
4 touches
1 conflict
0x042c6ea2…7a9a
0x34b655…2a6f
4 touches
1 conflict
0x19e483aa…2b28
0x34b655…2a6f
4 touches
1 conflict
0x31b39922…1e66
0x34b655…2a6f
4 touches
1 conflict
0x74fd0a9b…3aaa
0x34b655…2a6f
4 touches
1 conflict
0xdb392027…0308
0x34b655…2a6f
4 touches
1 conflict
0xdb392027…0309
0x34b655…2a6f
4 touches
1 conflict
0xe06bbb2e…9416
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 0x040ffbf257…95b9fd
Audit this contract →
← previous block·next block →recent activity