← previous blocknext block →recent activity
Analyzing
Block #93,188,252
16 transactions · 16 stateful · 2026-08-04 23:10:14 UTC
Parallelism
88/100
Blocked
19%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #93,188,252 · 16 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w07w112w013w114w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe66213ec…4e22
0x34b655…2a6f
4 touches
1 conflict
0xdc56639d…8bb9
0x34b655…2a6f
4 touches
1 conflict
0xe2cf3629…9568
0x34b655…2a6f
4 touches
1 conflict
0x13306c72…fb14
0x34b655…2a6f
4 touches
1 conflict
0x32409e80…a396
0x34b655…2a6f
4 touches
1 conflict
0x3b4e6b38…bd6a
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x5d6e4470…4b4c
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 0xe66213ecfc…714e22
Audit this contract →
← previous block·next block →recent activity