← previous blocknext block →recent activity
Analyzing
Block #93,437,953
21 transactions · 19 stateful · 2026-08-05 20:05:40 UTC
Parallelism
71/100
Blocked
32%
Avg conflicts / tx
0.43
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,437,953 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w15w111w216w317w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x65bac65a…38c9
0x34b655…2a6f
6 touches
3 conflicts
0x69a45f39…39aa
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0xaa48195d…ffee
0x34b655…2a6f
4 touches
1 conflict
0xc01decc3…08a1
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xa8667a2e…b5e2
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
3 conflicts on slot 0x65bac65a1c…5d38c9
Audit this contract →
← previous block·next block →recent activity