← previous blocknext block →recent activity
Analyzing
Block #105,444,983
16 transactions · 14 stateful · 2026-09-16 23:01:10 UTC
Parallelism
81/100
Blocked
36%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #105,444,983 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w05w17w19w010w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xe2f8c65c…4dfe
0x34b655…2a6f
6 touches
3 conflicts
0x51fc8795…126f
0x34b655…2a6f
6 touches
3 conflicts
0xa6e7f29c…5d8c
0x34b655…2a6f
6 touches
3 conflicts
0x79ec4509…1f61
0x34b655…2a6f
4 touches
1 conflict
0x8bf661cb…bcd2
0x34b655…2a6f
4 touches
1 conflict
0x8dfa3fd4…d3a1
0x34b655…2a6f
4 touches
1 conflict
0x987859be…2686
0x34b655…2a6f
4 touches
1 conflict
0xc14861fc…8948
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
3 conflicts on slot 0xe2f8c65ce8…e14dfe
Audit this contract →
← previous block·next block →recent activity