← previous blocknext block →recent activity
Analyzing
Block #101,989,656
19 transactions · 18 stateful · 2026-09-04 19:59:28 UTC
Parallelism
74/100
Blocked
33%
Avg conflicts / tx
0.68
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #101,989,656 · 19 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
1w04w15w28w010w115w016w217w318w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x3a1711ab…1ee8
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xe09e365c…b22d
0x34b655…2a6f
4 touches
1 conflict
0x0f440ba4…627a
0x34b655…2a6f
4 touches
1 conflict
0x184e765d…08f6
0x34b655…2a6f
4 touches
1 conflict
0x59d2df30…aff2
0x34b655…2a6f
4 touches
1 conflict
0x61a11641…fef0
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 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity