← previous blocknext block →recent activity
Analyzing
Block #93,440,628
21 transactions · 18 stateful · 2026-08-05 20:19:06 UTC
Parallelism
67/100
Blocked
44%
Avg conflicts / tx
0.95
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #93,440,628 · 21 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w08w110w211w313w314w417w418w520w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5502e1cc…3910
0x34b655…2a6f
12 touches
15 conflicts
0xf4f9cac7…fd98
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0x228d47a0…0efa
0x34b655…2a6f
4 touches
1 conflict
0x361f4a1b…1f14
0x34b655…2a6f
4 touches
1 conflict
0x4bf77c60…a7a5
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
15 conflicts on slot 0x5502e1cc19…1a3910
Audit this contract →
← previous block·next block →recent activity