← previous blocknext block →recent activity
Analyzing
Block #101,300,444
37 transactions · 33 stateful · 2026-09-02 10:08:06 UTC
Parallelism
68/100
Blocked
52%
Avg conflicts / tx
1.3
Longest chain
12 deep
Execution timeline
did this block parallelize well?
view
block #101,300,444 · 37 txs across 12 waves · depth 12
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w05w17w08w111w012w013w014w115w116w217w322w025w226w227w229w430w531w632w733w834w935w1036w11
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xf8f1e808…a4fd
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xf0e8582d…e851
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
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
28 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity