← previous blocknext block →recent activity
Analyzing
Block #93,291,193
15 transactions · 14 stateful · 2026-08-05 07:47:47 UTC
Parallelism
80/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,291,193 · 15 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
2w03w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xad7cfcc0…c388
0x34b655…2a6f
4 touches
1 conflict
0xbde524f4…43bf
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
0x34b655…2a6f
4 touches
1 conflict
0xd821f566…435a
0x34b655…2a6f
3 touches
1 conflict
0x5cc78005…4877
0x34b655…2a6f
2 touches
0 conflicts
0x66812b79…4c80
0x34b655…2a6f
2 touches
0 conflicts
0x8e8d48a4…7a75
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 0xad7cfcc0a9…dac388
Audit this contract →
← previous block·next block →recent activity