← previous blocknext block →recent activity
Analyzing
Block #93,490,733
14 transactions · 13 stateful · 2026-08-06 00:30:59 UTC
Parallelism
64/100
Blocked
38%
Avg conflicts / tx
0.36
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #93,490,733 · 14 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w06w17w28w312w313w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd676e291…3ecf
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xe5bb3628…e5f1
0x34b655…2a6f
4 touches
1 conflict
0x0f2d78b1…7363
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37a
0x34b655…2a6f
4 touches
1 conflict
0x4e8c4408…d37b
0x34b655…2a6f
4 touches
1 conflict
0x58620f29…db5a
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
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 0xd676e29175…2b3ecf
Audit this contract →
← previous block·next block →recent activity