← previous blocknext block →recent activity
Analyzing
Block #102,230,529
26 transactions · 25 stateful · 2026-09-05 16:20:15 UTC
Parallelism
81/100
Blocked
56%
Avg conflicts / tx
1
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #102,230,529 · 26 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
1w02w13w06w111w012w114w215w116w317w018w119w220w321w422w423w224w325w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe0659a3f…90d9
0x000000…a032
10 touches
10 conflicts
0x34b1e500…7687
0x754704…b603
10 touches
10 conflicts
0x00000000…000b
0x78999c…f371
10 touches
10 conflicts
0x00000000…000f
0x78999c…f371
10 touches
10 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x4188cc5f…2d2e
0x34b655…2a6f
6 touches
3 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: 0x00000000…7da032
10 conflicts on slot 0xe0659a3f75…9f90d9
Audit this contract →
← previous block·next block →recent activity