← previous blocknext block →recent activity
Analyzing
Block #93,456,481
16 transactions · 15 stateful · 2026-08-05 21:38:48 UTC
Parallelism
63/100
Blocked
47%
Avg conflicts / tx
0.63
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #93,456,481 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w15w26w37w49w513w114w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x70a7b5d6…fe0e
0x34b655…2a6f
8 touches
6 conflicts
0x84e3ed5a…1678
0x34b655…2a6f
6 touches
3 conflicts
0xd5eb243a…a3fc
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xb0651d04…fb27
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x9e121a54…06fb
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
6 conflicts on slot 0x70a7b5d69a…6cfe0e
Audit this contract →
← previous block·next block →recent activity