← previous blocknext block →recent activity
Analyzing
Block #93,195,312
9 transactions · 8 stateful · 2026-08-04 23:45:43 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.33
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,195,312 · 9 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
1w02w13w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0x08330b36…ae29
0x34b655…2a6f
4 touches
1 conflict
0x704139d1…8e57
0x34b655…2a6f
4 touches
1 conflict
0xdd190722…ecae
0x34b655…2a6f
4 touches
1 conflict
0x31eef44e…3694
0x34b655…2a6f
2 touches
0 conflicts
0x38c44a09…599d
0x34b655…2a6f
2 touches
0 conflicts
0x588ba065…f516
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
1 conflict on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity