← previous blocknext block →recent activity
Analyzing
Block #105,749,427
21 transactions · 20 stateful · 2026-09-18 00:33:28 UTC
Parallelism
81/100
Blocked
40%
Avg conflicts / tx
0.76
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #105,749,427 · 21 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
1w02w13w14w25w313w014w215w318w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc5847c4d…a65c
0x34b655…2a6f
8 touches
6 conflicts
0x49890ced…6f23
0x34b655…2a6f
8 touches
6 conflicts
0x1040ff5a…d433
0x34b655…2a6f
6 touches
3 conflicts
0x7aad02c6…b979
0x34b655…2a6f
6 touches
3 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0x72b3dc81…d09e
0x34b655…2a6f
4 touches
1 conflict
0x761bd1e6…ad68
0x34b655…2a6f
4 touches
1 conflict
0x81244465…8226
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 0xc5847c4d32…49a65c
Audit this contract →
← previous block·next block →recent activity