← previous blocknext block →recent activity
Analyzing
Block #93,306,167
70 transactions · 67 stateful · 2026-08-05 09:03:04 UTC
Parallelism
96/100
Blocked
4%
Avg conflicts / tx
0.06
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,306,167 · 70 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
5w08w09w110w265w066w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xf657e079…4fca
0x34b655…2a6f
4 touches
1 conflict
0xc824469a…6426
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xea02471d…1542
0x34b655…2a6f
4 touches
1 conflict
0xf3d10975…0d07
0x34b655…2a6f
4 touches
1 conflict
0x05e1eba1…6491
0x34b655…2a6f
4 touches
1 conflict
0x30b63238…6714
0x34b655…2a6f
4 touches
1 conflict
0x34a1ee7e…fb20
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 0xf657e0797d…524fca
Audit this contract →
← previous block·next block →recent activity