← previous blocknext block →recent activity
Analyzing
Block #93,678,479
18 transactions · 17 stateful · 2026-08-06 16:14:48 UTC
Parallelism
78/100
Blocked
35%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #93,678,479 · 18 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
2w05w06w17w08w19w011w112w113w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x52b477bc…7ccf
0x34b655…2a6f
8 touches
6 conflicts
0x002fed35…79fa
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0xd676e291…3ecf
0x34b655…2a6f
4 touches
1 conflict
0x77d99fc6…700f
0x065c9d…c394
3 touches
1 conflict
0x1e659cb0…c9df
0x065c9d…c394
3 touches
1 conflict
0x5c35957d…a2ff
0x065c9d…c394
3 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 0x52b477bcb8…5d7ccf
Audit this contract →
← previous block·next block →recent activity