← previous blocknext block →recent activity
Analyzing
Block #101,324,344
30 transactions · 23 stateful · 2026-09-02 12:08:21 UTC
Parallelism
87/100
Blocked
30%
Avg conflicts / tx
0.37
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #101,324,344 · 30 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w03w14w28w012w115w216w318w019w128w029w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x2b54cadb…4425
0xd18b7e…414b
6 touches
3 conflicts
0xa1087a5c…66c4
0x754704…b603
6 touches
3 conflicts
0x3e1e8e54…9c83
0x2a68ba…90c5
6 touches
3 conflicts
0xac1d8502…1ad6
0x40c49f…2af0
4 touches
1 conflict
0xf8f1e808…a4fd
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x070a562a…8147
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 0xca841faae5…71486a
Audit this contract →
← previous block·next block →recent activity