← previous blocknext block →recent activity
Analyzing
Block #93,279,741
23 transactions · 18 stateful · 2026-08-05 06:50:12 UTC
Parallelism
87/100
Blocked
44%
Avg conflicts / tx
0.43
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #93,279,741 · 23 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
1w010w011w112w113w014w115w216w217w018w119w020w121w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x724cd9ff…6684
0xe4f6e7…9657
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x44ad89ba…cf83
0xe4f6e7…9657
6 touches
3 conflicts
0x724cd9ff…6684
0x0cc9b2…7777
6 touches
3 conflicts
0x00000000…0008
0x0ea966…0742
6 touches
3 conflicts
0xc824469a…642d
0x34b655…2a6f
4 touches
1 conflict
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x49890ced…6f23
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: 0xe4f6e757…919657
3 conflicts on slot 0x724cd9ff19…4c6684
Audit this contract →
← previous block·next block →recent activity