← previous blocknext block →recent activity
Analyzing
Block #101,967,382
23 transactions · 20 stateful · 2026-09-04 18:06:31 UTC
Parallelism
74/100
Blocked
40%
Avg conflicts / tx
0.74
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #101,967,382 · 23 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
1w04w07w08w09w110w112w213w017w118w220w321w422w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x9ac96109…3059
0x405b63…7777
6 touches
3 conflicts
0x00000000…0003
0x24bf77…906e
6 touches
3 conflicts
0x00000000…0000
0x24bf77…906e
6 touches
3 conflicts
0xc9190cc1…8088
0x3bd359…433a
6 touches
3 conflicts
0x4546ebad…b908
0x34b655…2a6f
4 touches
1 conflict
0x5eb187dd…b1d6
0x34b655…2a6f
4 touches
1 conflict
0x7aad02c6…b979
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity