← previous blocknext block →recent activity
Analyzing
Block #100,920,563
22 transactions · 21 stateful · 2026-09-01 02:16:37 UTC
Parallelism
73/100
Blocked
48%
Avg conflicts / tx
0.73
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #100,920,563 · 22 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
3w06w17w28w19w010w111w012w114w316w017w119w220w421w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x41c56387…a8f6
0x34b655…2a6f
8 touches
6 conflicts
0x1db5837f…1264
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…004c
0x80c745…7210
4 touches
1 conflict
0x09106a95…1467
0x33176b…e078
4 touches
1 conflict
0x23529e13…6f25
0x34b655…2a6f
4 touches
1 conflict
0x3014896c…6c3d
0x34b655…2a6f
4 touches
1 conflict
0xac2a0273…721b
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 0x41c5638713…86a8f6
Audit this contract →
← previous block·next block →recent activity