← previous blocknext block →recent activity
Analyzing
Block #93,556,958
15 transactions · 14 stateful · 2026-08-06 06:03:54 UTC
Parallelism
80/100
Blocked
29%
Avg conflicts / tx
0.4
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,556,958 · 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
2w03w14w05w18w29w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x002fed35…79fa
0x2a68ba…90c5
6 touches
3 conflicts
0xfa831e2b…7b14
0x851145…3f07
5 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
4 touches
1 conflict
0xc824469a…6425
0x34b655…2a6f
4 touches
1 conflict
0x11b69a7e…334e
0x01bff4…1071
4 touches
1 conflict
0x8d5fc820…1750
0x34b655…2a6f
4 touches
1 conflict
0x42d5e8f3…5930
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity